Fix building additional abstract type edges #2259
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
As we build the query graph, some edges are added between abstract types to avoid type explosion when we can. Unfortunately, in some cases, adding those edge was incorrect and we need to type-explode due to some specific different between subgraphs on the definition of the types involved. This fixes this issue. Fixes apollographql#361
👷 Deploy request for apollo-federation-docs pending review.Visit the deploys page to approve it
|
|
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 is the modified version of #2194 that I mentioned in my comment, but creating a separate PR as I can't easily push there. |
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.
As we build the query graph, some edges are added between abstract types to avoid type explosion when we can. Unfortunately, in some cases, adding those edge was incorrect and we need to type-explode due to some specific different between subgraphs on the definition of the types involved. This fixes this issue.
Fixes #361