feat: add pipeline description with placeholders #1634
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Description
Added a new
PipelineDescriptioncomponent that enhances pipeline descriptions with dynamic placeholder support. This component allows users to include variables in descriptions that get resolved at runtime, such as${arguments.InputName}and date formats like${date.timestamp}.The component provides both display and editing modes, with a click-to-edit interface when not in read-only mode. It's now used in both the Pipeline Editor and Run Details views.
Pipeline Description
Placeholder Syntax
The pipeline description supports dynamic placeholders that are resolved at submission time:
${arguments.<input_name>}${arguments.Dataset Path}→/data/train.csv${date.timestamp}1705257600${date.short}1/14/26, 3:00 PM${date.long}January 14, 2026 at 3:00:00 PM ESTExample
If a pipeline has:
Training PipelineTraining on ${arguments.Dataset} - ${date.short}When submitted with argument
Dataset = "ImageNet", the run will display:Type of Change
Checklist
Test Instructions
Screen Recording 2026-01-15 at 12.38.37 AM.mov (uploaded via Graphite)
${arguments.InputName}or${date.short}