Conversation
This will allow to use syntax highlighting, without linting.
|
Looking forward to this being merged |
|
Has the whole project been abandoned? |
This file contains hidden or 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 will allow to use syntax highlighting, without linting.
Linting don't work very well in all projects and for all queries. For example if there is multiple statements in the query, like
DDL query
Or when you want to use database which has different database name than the username, (limited by
sql-lintmodule).But the highlighting is working well, so be able to use at least the syntax highlighting when linting is not working, may be very useful for some users.