Add CQL language support #3811
Open
Add CQL language support #3811
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull requests add support for CQL - Contextual Query Language. This is a query language used in SRU (Search/Retrieve via URL), standardized by the Library of Congress and part of an OASIS Standard. It is often used in library search engines and can be used to query key-value based datasets.
Note that this grammar/language is mostly used as a single query (line), not multiple query statements together, as parsing can be a bit ambiguous. Basically, any identifier can function as index, operator or value of a search clause triple...
So, the recommendation is to only use inline
<code>for highlighting, and never try to combine multiple query over line-breaks in<pre><code>blocks.The Spec is not quite clear whether line breaks are to be ignored as standard whitespaces, and can be part of string values, or if there shouldn't be any. So, I did not insert an artificial line break separator (which would make some things easier).
Refs: