Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix introspection false mismatch: defaultValue list of objects #6075

Merged
merged 1 commit into from
Sep 27, 2024

Conversation

SimonSapin
Copy link
Contributor

In GraphQL introspection response, the defaultValue of an anrgument or input object field is represented as a JSON string that contains GraphQL syntax. If that value contains a GraphQL object value, graphql-js seems to sort its contents by input object field name whereas apollo-compiler preserves the source ordering.

This causes introspection JSON responses to be different in a way that we consider not to be meaningful: object values are semantically unordered maps. Introspection "both" mode already had code to sort object values in order to ignore these differences, but was missing the case where defaultValue is not directly an object value but a list value of object values.


Checklist

Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.

  • Changes are compatible1
  • Documentation2 completed
  • Performance impact assessed and acceptable
  • Tests added and passing3
    • Unit Tests
    • Integration Tests
    • Manual Tests

Exceptions

Note any exceptions here

Notes

Footnotes

  1. It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this.

  2. Configuration is an important part of many changes. Where applicable please try to document configuration examples.

  3. Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions.

In GraphQL introspection response, the `defaultValue` of an anrgument
or input object field is represented as a JSON string that contains
GraphQL syntax. If that value contains a GraphQL object value,
graphql-js seems to sort its contents by input object field name
whereas apollo-compiler preserves the source ordering.

This causes introspection JSON responses to be different in a way
that we consider not to be meaningful: object values are semantically
unordered maps.
Introspection "both" mode already had code to sort object values in order
to ignore these differences, but was missing the case where `defaultValue`
is not directly an object value but a list value of object values.
Copy link
Contributor

@SimonSapin, please consider creating a changeset entry in /.changesets/. These instructions describe the process and tooling.

@SimonSapin SimonSapin merged commit 9ffcddc into dev Sep 27, 2024
14 checks passed
@SimonSapin SimonSapin deleted the simon/default-value-list-of-objects branch September 27, 2024 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants