Parameterized Graphs (aka Module
s)
#109
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Warning
This branch is still a work-in-progress.
We'd like the ability to be able to re-use Substate graphs and use them as nodes in other graphs. There's a two main components to this that I've been working on in this branch: parameterizing graph "inputs" and representing a graph as another node.
We're kicking around the idea of naming this
Module
for now - this will be exposed as a node that can be used in other graphs.Right now this change would support using a subgraph through the JSON serialization directly in the
Module
node, but when we implement publishing these modules we'd also like to reference them byid
(or possiblename
oruri
)The result will enable the following sort of SDK usage:
Related server implementation: https://github.com/SubstrateLabs/substrate/pull/1401