Skip to main content

Module registry

Module registry 

Source
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§

NodeRegistry
A per-S registry 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_input had been called with the Rust value), and anything else arrives as a wrapped serde_json::Value.

Type Aliases§

NodeFactory
Factory building a node instance from its definition (config blob included) and the dependency-injection context.
ValueFactory
Converts a JSON static-input value from a GraphDef into a typed BspValue at instantiation time.