Repository navigation
[Fusion] Fix ignored non-accessible fields failing composition with UNREACHABLE_SOURCE_FIELD - #10685
Merged
Merged
Conversation
…NREACHABLE_SOURCE_FIELD
Contributor
Patch coverage100.0% of changed lines covered (10/10)
Project coverage: 59.4% (316767/533315 lines) |
This was referenced Oct 25, 2026
Merged
This was referenced Nov 1, 2026
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.
Composition failed with UNREACHABLE_SOURCE_FIELD for fields that a source schema's settings list under
satisfiability.ignoredNonAccessibleFields, so schemas that composed before #10683 broke. The rule now skips any field whose coordinate is in that list, whatever paths are listed. This fixes the failing Nitro testFusionComposeCommandTests.Compose_IgnoredNonAccessibleFields, and the docs now say that this setting also silences UNREACHABLE_SOURCE_FIELD.