Expand description
The node & condition registry: the engine/definition separation made concrete.
Consumers register their node types (as factories), named routing predicates, and
mergers; the engine instantiates a GraphDef against the
registry. A GUI can then load, edit, save, and instantiate graphs — the full n8n
loop. Registries are per-S: consumers with multiple state types build one registry
per state type.
Node config schemas are consumer-owned and consumer-versioned (e.g. version inside the
config blob as {"v": 2, ...}); the engine stays out of it.
Structs§
- Node
Registry - A per-
Sregistry of node factories, named conditions, and mergers.
Functions§
- default_
value_ factory - The default static-input mapping: JSON bools/numbers/strings become typed values
(so dataflow nodes downcast them exactly as if
set_static_inputhad been called with the Rust value), and anything else arrives as a wrappedserde_json::Value.
Type Aliases§
- Node
Factory - Factory building a node instance from its definition (config blob included) and the dependency-injection context.
- Value
Factory - Converts a JSON static-input value from a
GraphDefinto a typedBspValueat instantiation time.