Stable order in introspection output #1239
Merged
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.
Follows #1237
Related to #1134
The type list sent from juniper through introspection to
GraphiQL
has random (but deterministic) order currently (based on FNV string hash of the type name).Inspired by #1237, I was interested in improving this.
This PR applies a sort order quite similar to the SDL sorter. The introspection data has a slightly different layout, but comparable.
To verify that the order is nice, stable and deterministic I removed the test sorter from the
schema_introspection
test.