Fix identifying psql parameters followed by comma #56
Conversation
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
MasterOdin
force-pushed
the
fix-psql-parameters
branch
from
aac74da to
5a5910d
Compare
|
Sorry just saw this. Good stuff |
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.
Fixes #54
PR fixes a bug where if a psql parameter was followed by a non-number character (e.g. a comma), it would include the character in the parameter value. The issue was that we were only rewinding our state when we broke out of value identifier for a whitespace character, when it should be any character, which is covered by checking for
nextChar !== null.Included a test both within the tokenizer where the bug was, as well at the identify level just for sanity checking.