Skip to content

Conversation

Coelho04
Copy link

@Coelho04 Coelho04 commented Oct 6, 2025

Reported here #6727 (comment)

An interface can be distributed across multiple source schemas, and each schema may implement that interface with different concrete types. The planner currently fails when you specify a type refinement for a concrete type that doesn't exist in the source schema that provides the field returning the distributed interface.
Since a source schema can only return the concrete types it actually defines, we can safely ignore inapplicable type refinements during planning.

@CLAassistant
Copy link

CLAassistant commented Oct 6, 2025

CLA assistant check
All committers have signed the CLA.

Copy link
Member

@tobias-tengler tobias-tengler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Thank you for your contribution :)
I took the liberty to clean up a bit and fix the Interface_Field_With_Only_Type_Refinements_Exclusive_To_Other_Schema test.

Once you sign the CLA, I can get this merged.

@tobias-tengler tobias-tengler changed the title [FUSION] Ignore inapplicable type refinements on abstract types [Fusion] Ignore inapplicable type refinements on abstract types Oct 6, 2025
@tobias-tengler tobias-tengler merged commit 6413a98 into ChilliCream:main-version-15 Oct 6, 2025
103 of 105 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants