Deparser: Add optional formatting/pretty printing #338
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
TODO: This is currently pulled from a not-yet-tagged version of libpg_query.
lfittl
force-pushed
the
deparse-pretty-print
branch
from
cee67f6 to
d2a2294
Compare
lfittl
changed the title
lfittl
changed the title
keiko713
approved these changes
Aug 15, 2025
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.
See pganalyze/libpg_query#293
We should hold off on merging until we have a tagged libpg_query release. For context, this was updated locally to the latest libpg_query
17-latesttip, through pointing theupdate_sourcetask to a local checkout, but we need to actually tag a release on libpg_query to make that task work as expected.