feature-version-based-syntax-linting #3
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.
What is the motivation?
When using an outdated version of the database in surrealist, i found it difficult to keep track of supported syntax for different versions of surreal
What does this change do?
It adds a linter extension that you can import and give a surreal version, it will give linter errors if the syntax is no longer or is yet to be supported by the given surreal version
What is your testing strategy?
I enter a dev env and i run the linter over the given syntax i wanted to test with the linter version set to a supported version, and then in an unsupported version and looked if the linter triggered
Is this related to any issues?
no
Have you read the Contributing Guidelines?