|
1 |
| -# VSCode Extension |
| 1 | +# Neo4j for VS Code Preview |
2 | 2 |
|
3 |
| -This is a VScode extension playground for testing the Cypher language server. |
| 3 | +## Getting started |
4 | 4 |
|
5 |
| -It's not yet published on the VSCode Marketplace, so to test it you need to run it locally. |
| 5 | +Open a file with `.cypher` extension after installing the extension from the VSCode marketplace. To enable database aware features (such as completing labels/functions), set up a connection to a neo4j instance using the settings described in the settings section below. |
6 | 6 |
|
7 |
| -For running it, compile the code first: |
| 7 | +### Feature Highlights |
8 | 8 |
|
9 |
| -``` |
10 |
| -npm install |
11 |
| -npm run build |
12 |
| -``` |
| 9 | +Our extension preview provides a rich set of features for working with Cypher, including: |
13 | 10 |
|
14 |
| -To launch a new VSCode window with the extension installed go to the `Run & Debug` tab (normally in the left pannel), select and run `VSCode Playground` clicking on the play ▷ button. |
| 11 | +- Syntax highlighting |
| 12 | +- Syntax checking - both syntax and semantic errors (e.g. type errors, unknown labels etc.) |
| 13 | +- Autocompletion for Cypher keywords, functions, labels, properties, database names and more |
| 14 | +- Signature help for functions - shows the signature of the function while typing |
15 | 15 |
|
16 |
| -This will open a new window where we can open our folder of choice, create a file with `.cypher` extension and start typing cypher helped by the language support. |
| 16 | + |
17 | 17 |
|
18 |
| -## Plugin settings |
| 18 | +### Upcoming features |
19 | 19 |
|
20 |
| -For database aware features (such as autocompleting labels, procedure names, etc), you can connect to a running database (Aura, neo4j docker, etc) by tweaking the playground settings, in the opened window. |
| 20 | +We're working on adding more features to the extension, such as: |
21 | 21 |
|
22 |
| -The following settings are available in VSCode once the plugin is installed, which can be set either through the `Settings` menu on VSCode or by creating a `.vscode/settings.json` file in the window opened by the play button. |
| 22 | +- Easier database connection management |
| 23 | +- Embedded cypher support in other file types |
| 24 | +- REPL-like scratchpad for debugging queries |
| 25 | +- Automated formatting |
23 | 26 |
|
24 |
| -### Settings for database connection |
| 27 | +## Extension settings |
25 | 28 |
|
26 |
| -The following settings refer to the database connection used for signature loading, this will allow for autocomplete on Labels and Types. |
| 29 | +The following settings are available in VSCode once the plugin is installed, which can be set either through the `Settings` menu on VSCode or by editing your `.vscode/settings.json` file. |
27 | 30 |
|
28 |
| -- `cypherLSP.neo4j.connect`: If true it will attempt to connect to a Neo4j database to retrieve signature information. Defaults to `true`. |
| 31 | +- `cypherLSP.neo4j.connect`: If true it will attempt to connect to a Neo4j database to retrieve data used for completions. Defaults to `true`. |
29 | 32 | - `cypherLSP.neo4j.user`: Defaults to `"neo4j"`
|
30 | 33 | - `cypherLSP.neo4j.password`: Defaults to `"password"`
|
31 |
| -- `cypherLSP.neo4j.URL`: Defaults to `"bolt://localhost:7687"` |
32 |
| - |
33 |
| - |
| 34 | +- `cypherLSP.neo4j.URL`: Defaults to `"neo4j://localhost:7687"` |
34 | 35 |
|
35 | 36 | ### Debug
|
36 | 37 |
|
37 | 38 | - `cypherLSP.trace.server`: Traces the communication between VS Code and the language server for debugging purposes.
|
| 39 | + |
| 40 | +### Contributing |
| 41 | + |
| 42 | +We welcome your suggestions, ideas, bug reports and contributions on the project on our [github](https://github.com/neo4j/cypher-language-support). |
| 43 | + |
| 44 | +To build the project locally, see the [CONTRIBUTING.md](CONTRIBUTING.md) file at the root of the repository. |
0 commit comments