Skip to content

Commit 937543f

Browse files
mmarconMassimiliano MarconAnemyalenakhineika
authored
docs: README updates VSCODE-395 (#516)
* docs: README updates VSCODE-395 * Fixed typo Co-authored-by: Rhys <[email protected]> * Removed double "work with" Co-authored-by: Alena Khineika <[email protected]> * Do not mention legacy shell in "Quick access to the MongoDB Shell" * Reformatted table cells * Exclude `resources` from bundle * Added `Database` keyword for marketplace Looks like most of the extensions about databases use it singular vs plural. * CTA for demo video Using HTML on purpose to center the banner. This means I need to use an `img` tag and use the absolute URL because I doubt the marketplace gets it replaced when it's not in markdown. The banner will be visible in the README once the PR is merged. --------- Co-authored-by: Massimiliano Marcon <[email protected]> Co-authored-by: Rhys <[email protected]> Co-authored-by: Alena Khineika <[email protected]>
1 parent b250c97 commit 937543f

13 files changed

+39
-30
lines changed

.vscodeignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,3 +16,4 @@ webpack.test.config.js
1616
.eslintrc
1717
.eslintignore
1818
playgrounds/**
19+
resources

README.md

Lines changed: 36 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,14 @@
1-
# MongoDB for VS Code ![PREVIEW](https://img.shields.io/badge/-PREVIEW-orange)
1+
# MongoDB for VS Code
22

33
[![Build Status](https://github.com/mongodb-js/vscode/actions/workflows/test-and-build.yaml/badge.svg?branchName=main)](https://github.com/mongodb-js/vscode/actions/workflows/test-and-build.yaml)
44

5-
MongoDB for VS Code makes it easy to work with MongoDB, whether your own instance or in [MongoDB Atlas](https://www.mongodb.com/cloud/atlas/register).
5+
MongoDB for VS Code makes it easy to work with your data in MongoDB directly from your VS Code environment. MongoDB for VS Code is the perfect companion for [MongoDB Atlas](https://www.mongodb.com/cloud/atlas/register), but you can also use it with your self-managed MongoDB instances.
6+
7+
<p align="center">
8+
<a title="Watch the MongoDB for VS Code demo video" href="https://mdb.link/vs-code-demo-video">
9+
<img src="https://github.com/mongodb-js/vscode/raw/main/resources/screenshots/get-started.png" width="700" alt="MongoDB for VS Code demo video call to action">
10+
</a>
11+
</p>
612

713
## Features
814

@@ -13,20 +19,22 @@ MongoDB for VS Code makes it easy to work with MongoDB, whether your own instanc
1319
- Edit documents and save changes to the database
1420
- Get a quick overview of your schema and your indexes
1521

22+
Read more about this functionality in the [online documentation](https://www.mongodb.com/docs/mongodb-vscode/databases-collections/).
23+
1624
![Explore data with MongoDB for VS Code](resources/screenshots/explore-data.png)
1725

1826
### MongoDB Playgrounds
1927

20-
MongoDB Playgrounds are the most convenient way to prototype and execute CRUD operations and other MongoDB commands directly inside VS Code.
28+
[MongoDB Playgrounds](https://www.mongodb.com/docs/mongodb-vscode/playgrounds/) are the most convenient way to prototype and execute CRUD operations and other MongoDB commands directly inside VS Code.
2129

22-
- Prototype your queries, aggregations, and MongoDB commands with convenient syntax highlighting and intelligent autocomplete for MongoDB shell API, BSON types, MQL operators, aggregation stage snippets, system variables, and for database, collection, and field names.
30+
- Prototype your queries, aggregations, and MongoDB commands with convenient syntax highlighting and intelligent autocomplete for MongoDB Shell API, BSON types, MongoDB Query API, system variables, and for database, collection, and field names.
2331
- Run your playgrounds and see the results instantly. Click the play button in the tab bar to see the output.
2432
- Edit documents returned by your playground.
25-
- Save your playgrounds in your workspace and use them to document how your application interacts with MongoDB.
33+
- Save your playground together with your application code to always have a place where all your queries are documented and can be tested just with one click.
2634

2735
![Playgrounds](resources/screenshots/playground.png)
2836

29-
_Make sure you are connected to a server or cluster before using a playground. You can't run a playground and you won't get completions if you are not connected._
37+
_Note: Make sure you are connected to a server or cluster before using a playground. You can't run a playground and you won't get intelligent completions if you are not connected._
3038

3139
#### From Query API to your favorite language
3240

@@ -38,21 +46,21 @@ Select queries and aggregations within your Playground files and translate them
3846
* Python 3
3947
* Ruby
4048

41-
![Query Translator](resources/screenshots/query-translator.png)
49+
![Export to language](resources/screenshots/export-to-language.gif)
4250

4351
### Document Editing
4452

45-
MongoDB for VS Code makes it extremely easy to make changes to documents in your collections. You can open documents in an editor tab, edit them and save the changes back to MongoDB.
53+
Editing documents with MongoDB for VS Code is as natural as editing any file in the code editor. Open a document in an editor tab, edit it, and save the changes back to MongoDB.
4654

47-
![Document editing](resources/screenshots/edit.png)
55+
![Document editing](resources/screenshots/edit.gif)
4856

4957
### Quick access to the MongoDB Shell
5058

51-
Launch the MongoDB Shell from the command palette to quickly connect to the same cluster you have active in VS Code.
59+
Launch the [MongoDB Shell](https://www.mongodb.com/products/shell) from the command palette to quickly connect to the same cluster you have active in VS Code.
5260

5361
![MongoDB Shell](resources/screenshots/shell-launcher.png)
5462

55-
_The shell binary needs to be in your `$PATH`. The shell binary can be either the new [MongoDB Shell](https://www.mongodb.com/products/shell) (`mongosh`) or the legacy `mongo` shell. In the extension's settings you can switch between the two._
63+
_Note: The `mongosh` binary needs to be in your `$PATH`. You can download the `mongosh` from the [MongoDB Download Center](https://www.mongodb.com/try/download/shell)._
5664

5765
### Terraform snippet for MongoDB Atlas
5866

@@ -62,27 +70,26 @@ If you use Terraform to manage your infrastructure, MongoDB for VS Code helps yo
6270

6371
## Extension Settings
6472

65-
- `mdb.shell`: The MongoDB shell to use (The new `mongosh` or the legacy `mongo`).
66-
- `mdb.showMongoDBConnectionExplorer`: Show or hide the MongoDB Connection explorer.
67-
- `mdb.showMongoDBPlaygrounds`: Show or hide the MongoDB Playgrounds explorer.
68-
- `mdb.showMongoDBHelpExplorer`: Show or hide the MongoDB Help explorer.
69-
- `mdb.defaultLimit`: The number of documents to fetch when viewing documents from a collection.
70-
- `mdb.confirmRunAll`: Show a confirmation message before running commands in a playground.
71-
- `mdb.confirmDeleteDocument`: Show a confirmation message before deleting a document in the tree view.
72-
- `mdb.excludeFromPlaygroundsSearch`: Exclude files and folders while searching for playground in the the current workspace.
73-
- `mdb.connectionSaving.hideOptionToChooseWhereToSaveNewConnections`: When a connection is added, a prompt is shown that let's the user decide where the new connection should be saved. When this setting is checked, the prompt is not shown and the default connection saving location setting is used.
74-
- `mdb.connectionSaving.defaultConnectionSavingLocation`: When the setting that hides the option to choose where to save new connections is checked, this setting sets if and where new connections are saved.
75-
- `mdb.useDefaultTemplateForPlayground`: Choose whether to use the default template for playground files or to start with an empty playground editor.
76-
- `mdb.uniqueObjectIdPerCursor`: The default behavior is to generate a single ObjectId and insert it on all cursors. Set to true to generate a unique ObjectId per cursor instead.
77-
- `mdb.sendTelemetry`: Opt-in and opt-out for diagnostic and telemetry collection.
78-
79-
![Settings](resources/screenshots/settings.png)
80-
73+
| Setting | Description | Default |
74+
|-------------------------------------------------------------------------- |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |---------------------------------------------------------------------------------------------------------------------------- |
75+
| `mdb.shell` | The MongoDB shell to use ( `mongosh` or the legacy `mongo` ). | `mongosh` |
76+
| `mdb.showMongoDBConnectionExplorer` | Show or hide the MongoDB Connection explorer. | `true` |
77+
| `mdb.showMongoDBPlaygrounds` | Show or hide the MongoDB Playgrounds explorer. | `true` |
78+
| `mdb.showMongoDBHelpExplorer` | Show or hide the MongoDB Help panel. | `true` |
79+
| `mdb.defaultLimit` | The number of documents to fetch when viewing documents from a collection. | `10` |
80+
| `mdb.confirmRunAll` | Show a confirmation message before running commands in a playground. | `true` |
81+
| `mdb.confirmDeleteDocument` | Show a confirmation message before deleting a document in the tree view. | `true` |
82+
| `mdb.excludeFromPlaygroundsSearch` | Exclude files and folders while searching for playground files in the current workspace. | Refer to [`package.json`](https://github.com/mongodb-js/vscode/blob/7b10092db4c8c10c4aa9c45b443c8ed3d5f37d5c/package.json) |
83+
| `mdb.connectionSaving.`<br>`hideOptionToChooseWhereToSaveNewConnections` | When a connection is added, a prompt is shown that let's the user decide where the new connection should be saved. When this setting is checked, the prompt is not shown and the default connection saving location setting is used. | `true` |
84+
| `mdb.connectionSaving.`<br>`defaultConnectionSavingLocation` | When the setting that hides the option to choose where to save new connections is checked, this setting sets if and where new connections are saved. | `Global` |
85+
| `mdb.useDefaultTemplateForPlayground` | Choose whether to use the default template for playground files or to start with an empty playground editor. | `true` |
86+
| `mdb.uniqueObjectIdPerCursor` | The default behavior is to generate a single ObjectId and insert it on all cursors. Set to true to generate a unique ObjectId per cursor instead. | `false` |
87+
| `mdb.sendTelemetry` | Opt-in and opt-out for diagnostic and telemetry collection. | `true` |
8188
## Additional Settings
8289

8390
### Autocomplete
8491

85-
_These global settings affect how MongoDB for VS Code provides intelligent autocomplete inside snippets and string literals (off by default). Changing the default configuration may affect the behavior and performance of other extensions and of VS Code itself. If you do not change the default settings, you can still trigger intelligent autocomplete inside a snippet or string literal with `Ctrl+Space`._
92+
_Note: these global settings affect how MongoDB for VS Code provides intelligent autocomplete inside snippets and string literals (off by default). Changing the default configuration may affect the behavior and performance of other extensions and of VS Code itself. If you do not change the default settings, you can still trigger intelligent autocomplete inside a snippet or string literal with `Ctrl+Space`._
8693

8794
- `editor.suggest.snippetsPreventQuickSuggestions`: By default, VS Code prevents code completion in snippet mode (editing placeholders in inserted code). Setting this to `false` allows snippet (eg. `$match`, `$addFields`) and field completion based on the document schema for the `db.collection.aggregate()` expressions.
8895
- `editor.quickSuggestions`: By default, VS Code prevents code completion inside string literals. To enable database names completions for `use('dbName')` expression use this configuration:
@@ -97,7 +104,7 @@ _These global settings affect how MongoDB for VS Code provides intelligent autoc
97104

98105
### Syntax Highlighting
99106

100-
The MongoDB playgrounds are JavaScript files, which causes JavaScript syntax highlighting to override any customizations made to the MongoDB syntax colors.
107+
MongoDB playgrounds are JavaScript files, which causes JavaScript syntax highlighting to override any customizations made to the MongoDB syntax colors.
101108

102109
Currently, there is no way to resolve this except for turning off semantic highlighting for a current workspace, or for all themes that are being used by setting `editor.semanticHighlighting.enabled` to `false`.
103110

package.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
2-
"preview": true,
2+
"preview": false,
33
"name": "mongodb-vscode",
44
"displayName": "MongoDB for VS Code",
55
"description": "Connect to MongoDB and Atlas directly from your VS Code environment, navigate your databases and collections, inspect your schema and use playgrounds to prototype queries and aggregations.",
@@ -24,6 +24,7 @@
2424
"MongoDB",
2525
"MongoDB Atlas",
2626
"MQL",
27+
"Database",
2728
"Databases"
2829
],
2930
"icon": "images/mongodb.png",

resources/screenshots/edit.gif

3.1 MB
Loading

resources/screenshots/edit.png

-563 KB
Binary file not shown.
-319 KB
Loading
1.93 MB
Loading
37.3 KB
Loading
-51.3 KB
Loading
-612 KB
Binary file not shown.

0 commit comments

Comments
 (0)