feat: Upgrades to sqltk v0.6.0 #212
Merged
Merged
Conversation
…, with corresponding adjustments to accommodate the parser upgrade.
damncabbage
force-pushed
the
rh/bump-sqltk
branch
from
e773fe9 to
ea904c1
Compare
freshtonic
approved these changes
Apr 30, 2025
freshtonic
left a comment
freshtonic
left a comment
Contributor
There was a problem hiding this comment.
Yep, looks fairly mechanical.
The token span shenanigans add a bit of noise but I can't see how we can avoid that.
LGTM! Thanks @damncabbage
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
2 participants
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:
sqltk::parser.0.52.0->0.53.0-...upgrade.sqltk-parser, using the re-export instead.