From 72d2835efbbef70ea48c70529d8534b5cc8d2e74 Mon Sep 17 00:00:00 2001 From: Michael Macaulay <56690114+MichaelMacaulay@users.noreply.github.com> Date: Tue, 8 Apr 2025 14:27:33 -0400 Subject: [PATCH 1/2] Update subgraph-composition.mdx --- website/src/pages/en/subgraphs/guides/subgraph-composition.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/en/subgraphs/guides/subgraph-composition.mdx index 88ebf9d97dca..ccc97ab45054 100644 --- a/website/src/pages/en/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/en/subgraphs/guides/subgraph-composition.mdx @@ -41,7 +41,7 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th - All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](https://thegraph.com/docs/en/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed - Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of - Source Subgraphs cannot use grafting on top of existing entities - Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly From 4cf428d7af2aab361867cef8cdd3bd264d34793e Mon Sep 17 00:00:00 2001 From: Michael Macaulay <56690114+MichaelMacaulay@users.noreply.github.com> Date: Tue, 8 Apr 2025 16:47:18 -0400 Subject: [PATCH 2/2] Adding periods --- .../subgraphs/guides/subgraph-composition.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/src/pages/en/subgraphs/guides/subgraph-composition.mdx b/website/src/pages/en/subgraphs/guides/subgraph-composition.mdx index ccc97ab45054..25b4bf00c2df 100644 --- a/website/src/pages/en/subgraphs/guides/subgraph-composition.mdx +++ b/website/src/pages/en/subgraphs/guides/subgraph-composition.mdx @@ -39,20 +39,20 @@ While the source Subgraph is a standard Subgraph, the dependent Subgraph uses th ### Source Subgraphs -- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs) +- All Subgraphs need to be published with a **specVersion 1.3.0 or later** (Use the latest graph-cli version to be able to deploy composable Subgraphs). - See notes here: https://github.com/graphprotocol/graph-node/releases/tag/v0.37.0 -- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed -- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of -- Source Subgraphs cannot use grafting on top of existing entities -- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly +- Immutable entities only: All Subgraphs must have [immutable entities](/subgraphs/best-practices/immutable-entities-bytes-as-ids/#immutable-entities) when the Subgraph is deployed. +- Pruning can be used in the source Subgraphs, but only entities that are immutable can be composed on top of. +- Source Subgraphs cannot use grafting on top of existing entities. +- Aggregated entities can be used in composition, but entities that are composed from them cannot performed additional aggregations directly. ### Composed Subgraphs -- You can only compose up to a **maximum of 5 source Subgraphs** -- Composed Subgraphs can only use **datasources from the same chain** -- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time -- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly -- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph) +- You can only compose up to a **maximum of 5 source Subgraphs.** +- Composed Subgraphs can only use **datasources from the same chain.** +- **Nested composition is not yet supported**: Composing on top of another composed Subgraph isn’t allowed at this time. +- Aggregated entities can be used in composition, but the composed entities on them cannot also use aggregations directly. +- Developers cannot compose an onchain datasource with a Subgraph datasource (i.e. you can’t do normal event handlers and call handlers and block handlers in a composed Subgraph). Additionally, you can explore the [example-composable-subgraph](https://github.com/graphprotocol/example-composable-subgraph) repository for a working implementation of composable Subgraphs