MongoDB for VS Code
MongoDB for VS Code lets you easily work with MongoDB directly from your VS Code environment. Using the MongoDB extension, you can:
- Connect to a MongoDB instance or cluster
- Navigate your databases and collections
- Prototype queries and aggregations
You can install the MongoDB extension from inside of VS Code via the VS Code Extension Marketplace. Help us improve the MongoDB for VS Code by posting your ideas and suggestions for improvements.
73 results found
-
DB Documantation
Adding the ability to add documentation on each db,collection,document,index etc...
for example :add an explenation on what this field is for in a document.
Then give the ability to generate a document with the db schema and all related details entered3 votes -
Add ObjectId() to intellisense
Add ObjectId() to .mongodb intellisense / autocomplete when indicating that an _id field is of ObjectId type
2 votes -
Intellisense for playground code
Hovering over getCollection and other supported methods doesn't show any intellisense. This would save us time from having to go to the docs and looking that method up. Also the sort method which I think its a normal JavaScript method doesn't show intellisense inside playground so please add some intellisense.
2 votes -
Better Failed to Connect Error Message
Currently, I get Failed to connect: connection <monitor> to X.Y.Z.W:27017 closed. It would be helpful to tell the user why that is or give a hint as to why the problem occurred. I have to keep it in the back of my mind that most of the time the issue is because my IP changed and my atlas doesn't have my ip whitelisted.
1 vote -
Set a default connection or auto detect a running MongoDB session
Automatically set up a connection via the MongoDB Extension instead of pasting the connection string manually every time.
Either by
1. detecting a running mongo session
2. Loading default connections, from a place on the system2 votes -
Connection based "theming"
Add the ability to color code playground tab and/or editor's background color in the playground based on the connection that is active.
Eg: default background for my localhost connection and a more colorful one for staging environment or production ones even.
3 votes -
Use Ctr-Enter to execute instuction where the cursor is.
Currently, is kind of tedius to execute a targeted line. Other editors accept Ctl-Enter to execute the line, which is very convenient.
5 votes -
Specify default database in Advanced Connection Settings form
The Create New Connection using the Advanced Connection Settings form does not provide a place to specify a default database. I'm specifically interested in this so I like running selected lines and it'd be a way to not include 'use(<db>)' with every query.
2 votes -
3 votes
-
make and export button and a delete collection item
make button to export collection to xls or any other spreadsheet file. And also make a button to remove collection items
2 votes -
Improvements to Terminal Shell (split)
It would be nice that When the VSC extension is added, it creates an entry in the integrated terminal settings (terminal.integrated.automated.windows/mac) like: -
"MongoDB": {
"path": "mongo",
"args": ["$Env:MDBCONNECTIONSTRING"]
}Which I can't currently get to work.
So that when I split a currently connected MongoDB intergrated terminal session, it spawns another mongo session with the same connection parameters at the same level.
Also at the moment $Env:MDBCONNECTIONSTRING only seems to be set when the MongoDB:Launch MongoDB Shell is run, not when a connection is made to the a MongoDB server (connections).
At the moment, if…
1 vote -
Handle 64bit numbers correctly
Javascript doesn't support 64bit internally, so if I try in Chrome/console: x = 285870311191169181, it becomes 285870311191169180, and the same thing happens in VS Code.
The solution would be to return a NumberLong("285870311191169181") text result.
In fact, it seems to be an issue in Compass as well... but it works in mongo shell.
Check the screenshot.1 vote -
We do not have to repeat use('db') every time
After executing use('db') we don't need to include the command with each run, especially when we want to run the selected line.
At present, if I run some selected lines to run from play ground it doesn't works if the lines doesn't includes the use('db') command.
11 votes -
Copy collection schema
Detailed Description
Ability to copy collection schema, Export schema to a typescript file,Context
So that we can use it (schema interface) for typescript. Basically It will infer types about collection.2 votes -
Please let the toolkit refresh database status more freequently
Please let the toolkit refresh database status more freequently.
You guys can having a try,to use playground create a new database,and then the database status doesnt appear the new database at all.Just need reloading VS Code and then i could found that there was a new database.1 vote -
Code linting when you save a .mongodb file
It would be nice to have the code cleaned up when you save a .mongodb file
1 vote -
Show UUID fields as UUID in document editor
I have a collection with documents containing UUID fields (standard, not legacy). When I browse those documents in the extension, they are shown like this:
{
"id": "5e58eae46015f74c61dd6af0",
"myuuid": {
"$binary": {
"base64": "ILGr2eKZSmqkQX1OZsoICQ==",
"subType": "04"
}
}
}I would have expected them to be shown as:
{
"id": "5e58eae46015f74c61dd6af0",
"myuuid": UUID("20b1abd9-e299-4a6a-a441-7d4e66ca0809")
}Robot 3T (for example) does this well. I think it would greatly help to read such values.
33 votes -
filter by database/collection name
would be nice to be able to filter by database/collection name in the connections panel, similar to what is found in MongoDB Compass.
4 votes -
"Table View" of Documents
As some others tools have, a way to view all documents from a collection in a table format with columns and lines. An 'click on header for sort' is well desirable.
21 votes -
New Playground Result tab for each query
When two playgrounds are run at once (e.g. two aggregations), the result of one overwrites the result of the other rather than opening a new 'Playground Result' tab.
The desired behaviour is for a new Playground Result tab to be opened per run (preferably numbered 'Playground Result 1', 'Playground Result 2', etc.
4 votes
- Don't see your idea?