chore: upgrade pg query and drop deprecated crates #188
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
juleswritescode
approved these changes
Jan 31, 2025
Collaborator
juleswritescode
left a comment
juleswritescode
left a comment
There was a problem hiding this comment.
Very nice!! :)
Should we pin the pg_query version on workspace level?
Collaborator
Author
good point - done! :) |
psteinroe
changed the title
Collaborator
|
|
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.
upgrade
pg_query.rsto latest.also:
libpg_querysubmodule to17-latestand updated the committree-sitter-sqlsubmodule to latest\c\rto fix lexer tests on windows (til: https://dev.to/pieter/why-windows-uses-rn-newlines-instead-of-n-126l)ahhh windows is still failing. I will just drop
pg_syntax- its not worth to fix the parser now :D