Add Cypher Query Language

[007vasy]

All tests are ok

Desciption

This PR adds the Cypher query language with the *.cypher and *.cyp extension.

*.cql is removed because:

• not mentioned here
• not part of the official recommendation
• ambigous based on the github search 4-5 different languages use it

The language is a graph query language https://opencypher.org/ and it's ISO recognition is WIP

regarding cypher extension There are already:

• 12k code results
• 411k package results
• 915k topic results

regarding cyp extension There are already:

• 1.4k code results
• 382k package results
• 895k topic results

So It would be great to have syntax highlighting on github (and later search as well) :)

Godspeed!

Checklist:

• I am adding a new language.
  • The extension of the new language is used in hundreds of repositories on GitHub.com.
    • Search results for each extension:
      • https://github.com/search?q=extension%3Acyp&type=Code
      • https://github.com/search?q=extension%3Acql&type=Code
      • https://github.com/search?q=extension%3Acypher&type=Code
  • I have included a real-world usage sample for all extensions added in this PR:
    • Sample source(s):
      • graphgems.*
        • https://github.com/neo4j/cypher-shell/blob/4.3/cypher-shell/src/test/resources/org/neo4j/shell/parser/graphgems.cypher
      • db_export_res.cypher:
        • https://neo4j.com/labs/apoc/4.1/export/cypher/
      • load_from_json.cypher:
        • https://neo4j.com/labs/apoc/4.1/import/load-json/
    • Sample license(s):
      • https://neo4j.com/docs/license/
      • https://github.com/neo4j/cypher-shell/blob/4.3/LICENSE.txt
    • Highlight license:
      • https://github.com/fredbenenson/sublime-cypher/blob/master/LICENSE.txt
    • Language license:
      • https://github.com/opencypher/openCypher/blob/master/LICENSE
  • I have included a syntax highlighting grammar: https://github.com/fredbenenson/sublime-cypher.git

[007vasy]

@lildude fixed the tests:
All tests are ok

[007vasy]

@lildude I want to make you proud!

[lildude]

Please replace the .cql and .cyp files with real-world usage samples.

I recommend adding at least two real world highly representative samples for the .cql extension as this extension is already used by SQL and good representative samples will help the classifier make a better guess.

[007vasy]

@lildude done

[lildude]

Wow! We don't need that many samples - two per extension is plenty. We also don't want duplicate content with different extensions as that doesn't train the classifier to differentiate between the extensions.

[007vasy]

the thing is with Cypher that all 3 extension can be used, it does not matter which is used so think from the training point of view it's good to have similar content with different extensions to help the classifier

[lildude]

the thing is with Cypher that all 3 extension can be used

In that case we only need one unique and most representative sample per extension, except for .cql due to it already being in use. Three identical copies of seven files is excessive and adds no value.

[007vasy]

@lildude done, left more examples for .cql and 1-1 for .cyp and .cyhper

[lildude]

Thanks. Please update the OP to point to the original source for each file and their relevant license.

I'll check the extensions meet our popularity requirements closer to merge time.

[007vasy]

@lildude

• updated OP
• added licenses
• removed one example

If you check the search results, it is going over by a mile to the popularity reqs

[007vasy]

and thank you for your patience!

[adriens]

➕ 1️⃣ 🗳️ 🙏

[adriens]

cf community/community#32466

[007vasy]

@lildude is there anything else needed?

[007vasy]

hi @lildude, @Alhadis what is the release schedule?

[lildude]

hi @lildude, @Alhadis what is the release schedule?

There isn't one. I make an release when I've got the time somewhere close to the next release of GitHub Enterprise Server as it's not a quick process. I'm also holding off approving PRs which add new languages until I'm close to release as it takes a lot more time to review than simple fixes.

"Be patient my young Padawan".

[adriens]

"Be patient my young Padawan".

AWESOME 🤣

[007vasy]

thanks for the update!

[adriens]

OMG 😮 You mean it will be availbale soon on GH ? When should I start to give it a try ❔

[007vasy]

the most probable point in time in the next github enterprise release, which could happen next week or 3 months from now

based on the github enterprise release schedule this could happen late october early november, best case

[adriens]

So let's 🤞 🐱

[007vasy]

@lildude can you at least allow the tests to run?

it should be fine I tested them on my fork, but I don't want to miss an other release window if possible

[adriens]

🤞 🙏 💯

[adriens]

Ready to 🚀 ❔

[lildude]

Yes, but it won't appear on GitHub until I make a release.

[007vasy]

@lildude do you have an estimate for a github release?

[lildude]

#6162

[adriens]

https://twitter.com/rastadidi/status/1593070750248075264