Repository navigation
[Fusion] Fix satisfiability validation skipping paths that reach an already visited type - #10673
Merged
Merged
Conversation
…lready visited type The validator deduplicated visits by (type, previous schema) and ignored the path, so a later path that reaches the same type could reuse the answer of an earlier path even when schema transitions differ, making the result depend on field declaration order. Visits are now keyed by the set of schemas that can still serve the path, plus the leaf where provided selections or requirements depend on it.
Contributor
Patch coverage98.7% of changed lines covered (542/549)
Uncovered changed lines (JSON){
"sha": "0f5798e0b80be432d4999a82d10e6471dac13828",
"files": [
{ "path": "src/HotChocolate/Fusion/src/Fusion.Composition/Satisfiability/SourceSchemaTransitionHelper.cs", "ranges": [[141, 142]] },
{ "path": "src/HotChocolate/Fusion/src/Fusion.Composition/Satisfiability/ProvidedSelectionSetKey.cs", "ranges": [[22, 22]] },
{ "path": "src/HotChocolate/Fusion/src/Fusion.Composition/SatisfiabilityValidator.cs", "ranges": [[436, 437]] },
{ "path": "src/HotChocolate/Fusion/src/Fusion.Composition/SatisfiabilityValidator.Viewer.cs", "ranges": [[155, 155], [166, 166]] }
]
}Project coverage: 59.3% (315637/532063 lines) |
This was referenced Oct 25, 2026
Merged
This was referenced Nov 1, 2026
This was referenced Nov 1, 2026
Closed
[nuget][SUI_Matcher]- Bump the sui-package-updates group with 21 updates
DFE-Digital/SUI_Matcher#424
Open
Bump HotChocolate.AspNetCore.Pipeline and HotChocolate.Fusion.AspNetCore
feddi-dev/feddi-gateway#109
Open
This was referenced Nov 8, 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.
Satisfiability validation checked each type once per source schema and skipped every later path that reached it the same way. Whether a field can be reached depends on the path, so the result depended on field order and some queries that cannot be planned still composed. Visits are now keyed by the set of schemas that can still serve the path, so every distinct path is checked. Schemas with such paths now fail composition. On a 745-subgraph schema, validation is faster (11.3 s to 2.6 s CPU) and reports the same errors.
Example:
{ objectUnShared { b } }cannot be planned becauseObjecthas no lookup in B. Composition passed unlessobjectUnSharedwas declared first. It now fails in both orders.