feat: sorting in cynic-parser pretty printing #1038
Merged
Conversation
This file contains 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
obmarg
changed the title
✅ Deploy Preview for cynic-querygen-web canceled.
|
obmarg
force-pushed
the
obmarg/vnnnpkmmoxkt
branch
2 times, most recently
from
d4d9d7e
to
fa27c20
Compare
obmarg
force-pushed
the
obmarg/vnnnpkmmoxkt
branch
from
fa27c20
to
9a23240
Compare
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.
Why are we making this change?
I'm writing some tests that compare the output of the same schema but from two different sources. I'm using cynic-parsers pretty printing to get consistent formatting of these two schemas. But the order that the definitions are output in between the two schemas does not match.
What effects does this change have?
Adds an optional setting to the cynic-parser formatting that causes the definitions & fields of the schema to be sorted prior to output.