Skip to content

docs: clarify source selection for composed schemas #1032

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
abisheik687 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify source selection for composed schemas #1032

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -472,6 +472,8 @@ query myQuery {
}
```

When two sources expose the same root field name, a GraphQL response alias does not select which source should execute that field. For example, `mainnet: pools` and `arbitrum: pools` are still two selections of the same composed `pools` field; the alias only changes the response key. In that case, disambiguate the sources before querying them by using transforms such as `rename` or `prefix`, or by adding explicit schema extension fields that delegate to the intended source.

You can also resolve conflicts, rename parts of the schema, add custom GraphQL fields, and modify the entire execution phase.

For advanced use-cases with composition, please refer to the following resources:
Expand Down