By default, no column yet
Optionalrest: JsonObjectReadonlycolumnsThe columns to keep, as given; validation checks them against the input
ReadonlyidUnique within the query and shown to users, e.g. filter101
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 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
In the spec's order: some columns, no column twice, then each column named and in the input, every column reported
Optionalerrors: string[]A new restrict with the same id, and these columns
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.
Keeps only some columns of its input (spec §7.4), in the input's order, not the order they were picked in: the engine's
selectkeeps the order it is given, so the emitter lists them in input order too.