You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The resolver for external1 will receive the required fields correctly. But external2 will get only the id field correctly filled. The difference is only the space.
Not sure what is the best way to fix this, but i assume this is driven from utils/getKeyFnForFederation. The function considers the first level keys (split by space) only.
I think we have 2 options:
keep current simple logic and split the key until first { - will still give you the whole subtree (might be more data than needed)
we could parse the whole selectionSet and recursively filter the root value.
The text was updated successfully, but these errors were encountered:
Issue workflow progress
Progress of the issue based on the
Contributor Workflow
Describe the bug
Given this snipped from a working supergraph schema.
The resolver for
external1
will receive therequired
fields correctly. Butexternal2
will get only theid
field correctly filled. The difference is only the space.Not sure what is the best way to fix this, but i assume this is driven from utils/getKeyFnForFederation. The function considers the first level keys (split by space) only.
I think we have 2 options:
{
- will still give you the whole subtree (might be more data than needed)The text was updated successfully, but these errors were encountered: