Blank screen always showing instead of query results (since recent UI update)

[dancherb]

When clicking on a collection from the extension panel, instead of seeing the results, a loader and then a blank screen appears.

The same occurs when writing a MongoDB Playground query and sending it - if there are results, only a blank screen appears.

If there are no results, a "no results" indicator does successfully show.

This appears related to a UI update in the last several weeks.

This same update also appears to have completely broken connecting to external MongoDB URIs (for example, hosted on MongoDB Atlas). So I've only been able to test this on localhost.

I'm on Windows 11, latest version of VSCode, latest version of extension.

[Anemy]

Hi @dancherb thanks for reporting this, I was able to reproduce. If you have a moment can you provide us an example of a document where this happens? I'm wondering if this happens with more than fields that can't be parsed by bson.

Looking into fixing this now, here's a ticket you can follow along: https://jira.mongodb.org/browse/VSCODE-768

[dancherb]

Thanks for looking into it 🙂

I couldn't find an example of a document where this didn't happen - it happened on all documents. Here's a super simple example I generated:

{
  "_id": {
    "$oid": "69c3f2b4feb8ccbf9b144ec1"
  },
  "test": "true"
}

I also saw the same happen when using my own string _id instead of the Mongoose ID - so that's not the issue.

I don't get the impression that it relates to the nature of individual documents. When there's just 1 or 2 documents in a collection and I click "2 documents" in the left-hand view, I get the same blank screen instead of seeing the list of documents.

If I click on a collection with 0 documents then I do see "No documents to display" correctly

[Anemy]

Hey @dancherb we just published a new version that should prevent the tab from crashing. It will now print the error we get when attempting to deserialize the document instead. This is a temporary fix, the main fix will be in VSCODE-772 later on.