Support the 'a' keyword in SPARQL lexer #1493
Merged
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
|
@kaefer3000 Thanks for doing the hard work and providing so much helpful information. This is a pretty straightforward fix but if you see anything wrong, please let me know! |
mattt
pushed a commit
to NSHipster/rouge
that referenced
this pull request
May 21, 2020
The case-sensitive keyword `a` is a valid keyword in SPARQL. At present, the SPARQL lexer does not recognise it as such. This commit fixes that error (the rule is similar to the one used in the Turtle lexer).
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.
The case-sensitive keyword
ais a valid keyword in SPARQL (reference). At present, the SPARQL lexer does not recognise it as such. This PR fixes that error (the rule is similar to the one used in the Turtle lexer).This fixes #1486.