Repository navigation
[Fusion] Reuse completed object types in Apollo representations - #10589
Merged
Merged
Conversation
Contributor
Patch coverage100.0% of changed lines covered (10/10)
Project coverage: 59.0% (311511/527765 lines) |
tobias-tengler
marked this pull request as ready for review
October 18, 2026 05:56
This was referenced Oct 25, 2026
Merged
This file contains hidden or 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
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.
Apollo representations decode
__typenameand resolve its schema type even when the completed object already carries its concrete type.This PR reuses the existing type and name when the actual type name matches the completed object’s concrete selection type. Missing, escaped and opaque type handling and the imported-snapshot fallback retain their contracts.
mainmainmainmain