ReadonlyhasWhether the saved JSON had an inputs key, which re-saving then writes too
ReadonlyidUnique within the query and shown to users, e.g. filter101
ReadonlyjsonThe saved JSON without id and inputs, kind included, e.g. {kind: 'future', rows: […]}
ReadonlykeyAssigned at construction from a monotonic sequence: the node's identity for change detection
ReadonlyrestThe keys of the node's saved JSON that this version does not know, kept so a re-save writes them back (PLAN §10.3); edits keep them too
Whether edits may change which nodes feed this one. Not for a node whose port semantics are unknown, such as an Unknown node.
Whether the node takes rows by their order, as a Limit does: the emitter then writes its input's order as a sort just before it (PLAN §11.4)
Labels for the input ports, shown on the edges that feed them
The named input slots, in order: none for a source, one for a unary transform, two for a binary one
The type it was saved with, e.g. future
The type discriminator, e.g. filter
A one-line description for the canvas and the details panel
The description without the values users typed, which may be sensitive, for logs and telemetry. By default the description, which has none.
Whether the node has none of the settings it needs yet, e.g. a Join with no key pair: the canvas shows it as not set, not by its description
Never valid: what the node does is unknown. It gives no reason, so it shows the generic error.
Optionalerrors: string[]The node to keep once its two inputs swap ports: by default this node. A node whose settings name its inputs by side, such as a Join's key columns, returns a new node (same id) with those settings swapped too.
A node of a type this version of Cube doesn't know, e.g. from a query saved by a newer version. It can be shown, inspected and edited around, but never validated or executed.
It gets one synthetic input port per input it had (
in0,in1, ...), so its edges are real connections: the graph rules, healing on removal and layout all apply to them. Since what its ports mean is unknown, it never accepts new inputs.It keeps the JSON it was saved as, so re-saving writes it back as it was (PLAN §4.10): everything but
idandinputs, which come from the query.