-
Notifications
You must be signed in to change notification settings - Fork 248
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
Reapply #2639 (with fix for #2680) #2687
Conversation
This commit reapplies #2639 with an additional fix related to reproducing and resolving #2680. The bug existed in the SelectionSet.contains logic in the final check to provide a ContainsResult. Here the lengths of the compared selection sets are used to determine subset or strictly equal. In the case that the __typename field was ignored up above, the comparison becomes invalid unless we offset the comparison by 1 to account for the non-existent field.
🦋 Changeset detectedLatest commit: c6eddfa The changes in this PR will be included in the next version bump. This PR includes changesets to release 7 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for apollo-federation-docs canceled.
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
This part is the fix, right?
|
@glasser correct |
oh that's more obvious in the non-backport :) |
This PR ports #2684 to the
2.5.x
release line.This commit reapplies #2639 with an additional fix related to reproducing and resolving #2680.
The bug existed in the
SelectionSet.contains
logic in the final check to provide aContainsResult
. Here the lengths of the compared selection sets are used to determine subset or strictly equal. In the case that the__typename
field was ignored up above, the comparison becomes invalid unless we offset the comparison by 1 to account for the non-existent field.