-
Notifications
You must be signed in to change notification settings - Fork 154
Publish composable subgraphs #919
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm! 🎆
- 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 composed on, but the composed entities on them cannot also use aggregations directly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- same suggestions as the above
Co-authored-by: Idalith <126833353+idalithb@users.noreply.github.com>
|
||
- 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be a relative URL.
No description provided.