jakeboone02 / cypher-query-language Goto Github PK

1. MATCH (a:Person {uuid: 'abc'}), (b:Person {uuid: '123'}) becomes MATCH (a:Person { uuid: 'abc' }), (b:Person {uuid: '123'}) (the spacing around the curly braces is only applied to the first item)
2. foreach(x in coll | delete x) capitalizes the special words (which is good), but it drops DELETE x to the next line. Not sure if this is intended or not, but it is less visually appealing and intuitive IMO

Originally posted by @ajmeese7 in #1 (comment)

Whenever I paste the default "Create an index" neo4j basic query into a .cypher file, none of the keywords are highlighted:

It works fine for CREATE INDEX ON (n.id), but doesn't work with the intermediate options.

I did try removing the newlines and having the query all on one line, but that did not make a difference.

Hi, whenever I use slavic characters they, are ignored by the syntax highlighter. It does result in not nice styling as for example here:

The following code does compile and runs without errors or warnings. In the standard all special characters in different languages are included as alphabetic characters:

https://neo4j.com/docs/cypher-manual/current/syntax/naming/

I assume, they need to be added somewhere on apropriate line in the '.syntaxes/cypher.tmLanguage' file?

When formatting this...

LOAD CSV WITH HEADERS FROM 'file:///recent-lineage.csv' AS line
WITH line

The output ends up like this...

LOAD CSV ///recent-lineage.csv' AS line
WITH HEADERS FROM 'file:
WITH line

Please consider publishing to the Open VSX Registry.

I use VSCodium because I want to use a truly open source code editor. The official VS Code binaries are proprietary, and they contain analytics code, which invades user privacy and slows the program down.

Unfortunately, due to licensing, only the official VS Code binaries are allowed to download extensions from the Visual Studio Marketplace. Because of this, as a VSCodium user, I depend on the Open VSX Registry for my extensions.

I hope you'll consider publishing your extension there.

Hey Jake,

I've been hunting around for your contact details but can't find them anywhere. I've been using this highlighter for years and was wondering if you would be interested in rolling up the changes into a new extension I've been working on for running Cypher queries in VS Code.

Feel free to email me at adam at neo4j dot com or open a PR if you are interested.

Whenever I run "Format Document: on a Cypher document, I get the VS Code popup that there are no formatters installed:

Since the extension README says this is supposed to act as a formatter, I assume that this is an error. Please correct me if I am wrong. Cheers!

RETURN apoc.map.merge({ a:1 }, {b:2})

results in

RETURN apoc.map.
MERGE ({ a:1 }, {b:2})

after formatting the document. merge is wrongly treated as keyword in this case. I suspect filtering for whitespace before and after merge should do the trick.