feat: parser sourcegen #4
Merged
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
- token type is now manual - added sibling token to control opening / closing tokens
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.
What kind of change does this PR introduce?
Adds source code generation for the
parsercrate.utility crates are added:
pg_query_proto_parserparses the pg_query proto file and exposes methods to read its contents in a simplified mannercodegenimplements procedural macros from the libpg_query proto definitionalso adds a bunch of example sql files to test the parser.
What is the current behavior?
Everything is hand-written, and / or incomplete.
What is the new behavior?
Everything that can be generated, is generated. The proto from libg_query is parsed, and based on its content, several enums and functions are generated.