Summary: Add support for setting node colors programmatically through the Pipeline Builder DSL, enabling color assignment via put_pipeline_builder / edit_pipeline_builder APIs and retrieval via get_pipeline_builder_definition.
Current Behavior:
-
Node colors (color groups) can only be assigned through the Pipeline Builder UI
-
The DSL definition returned by
get_pipeline_builder_definitiondoes not include any color information -
Attempting to add a
colorproperty to node metadata (inputs, transform paths, outputs, text nodes) results in a TypeScript type error:12
‘color’ does not exist in type ‘{ name: string; comment?: string | undefined; position: Position; id?: string | undefined; }’
-
Color data appears to be stored in a separate UI state layer (sandbox), not in the pipeline logic definition
Requested Behavior:
-
Add an optional
colorproperty (hex string, e.g."#147EB3") to the metadata objects for:-
PB.inputs.dataset()/PB.inputs.mediaSet() -
PB.transformPath() -
PB.outputs.dataset()/ other output types -
PB.textNode()
-
-
Include color information in the DSL code returned by
get_pipeline_builder_definition -
Allow color groups to be created/assigned as part of
put_pipeline_builder/edit_pipeline_buildercalls
Use Case:
When creating or modifying pipelines programmatically (e.g., via AI-assisted pipeline generation or automated pipeline templating), there is no way to apply visual styling to nodes. Users must manually open the UI and assign colors after every programmatic pipeline creation, which breaks the automation workflow. This is especially impactful for teams that use color coding conventions (e.g., blue for inputs, teal for transforms, green for outputs) as a standard practice.
Impact: Any workflow that programmatically creates or modifies Pipeline Builder pipelines cannot fully replicate the visual styling that users expect, requiring manual follow-up in the UI.