From 3ffa8359bc1738166e11c8c3e4e9c46ee4a39c86 Mon Sep 17 00:00:00 2001 From: Abisheik Date: Thu, 2 Jul 2026 15:46:05 +0530 Subject: [PATCH] docs: clarify source selection for composed schemas --- docs/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/README.md b/docs/README.md index 283b12d4..4125b538 100644 --- a/docs/README.md +++ b/docs/README.md @@ -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: