Skip to content

fix: Unable to perform joins from a nested object using @link - #1713

Open
Roshan931 wants to merge 1 commit into
spacecloud-io:masterfrom
Roshan931:prilog/fix-error-graphql-resolver-does-not-descend-into-08-21-2026-797082
Open

fix: Unable to perform joins from a nested object using @link#1713
Roshan931 wants to merge 1 commit into
spacecloud-io:masterfrom
Roshan931:prilog/fix-error-graphql-resolver-does-not-descend-into-08-21-2026-797082

Conversation

@Roshan931

Copy link
Copy Markdown

Fixes #1413

Root cause

GraphQL resolver does not descend into schema subtypes, so @link inside a nested object is never resolved

Changes

  • When execGraphQLDocument descends into a field with a selection set, it now swaps the active schema to the field's NestedObject fields for object-kind fields (in addition to the existing linked-table swap). This lets linked fields declared inside a subtype be discovered and trigger the linked read request. Added a focused regression test case exercising a mongo @link inside a nested object.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unable to perform joins from a nested object using @link

2 participants