Add SQL identifier case - new in SQL formatter 14.0.0 #172
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
worksofliam
approved these changes
Nov 27, 2023
There was a problem hiding this comment.
New config is awesome! preserve is a nice touch.
Thank you @chrjorgensen!
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 PR will
sqlFormat.identifierCaseto allow the user to have SQL identifier in lower- or uppercase or not changed. Default ispreserveto not change the identifier case unintentionally.With this support the following SQL statement
will be formatted like this (with identifiers set to uppercase and keywords to lowercase):