Currently, Dagu workflows often rely on plain text input fields for parameters. This can lead to configuration errors, typos, and ambiguity when users need to select from a predefined set of values.
I propose adding support for Radio Buttons and Dropdown Lists (Select) for workflow parameters in the Dagu UI, similar to the form pattern shown below (but also able to provide descriptions per PARAMS as shown in picture):
Visual Reference
The requested feature would allow users to define parameters that render as:
Radio Buttons: For single-choice selection from a short list (e.g., compute location, type).
Dropdowns: For single-choice selection from a longer list.
Example Use Case
Current Behavior: A user must manually type a value like us-east-1 or private into a text input. This risks typos (e.g., us-east-1 vs us-east-1 ) and doesn't enforce valid options.
Proposed Behavior: The workflow definition would support a ui or control schema that maps to specific UI elements.
Radio Buttons:
Label: Which compute location?
Options: [ us-east-1 ] [ us-west-2 ] [ eu-central-1 ]
Selection: User clicks one; the value is set.
Dropdown/Select:
Label: backend
Options: [ http://10.0.1.1:80 ] [ https://10.1.0.1:443 ]
Currently, Dagu workflows often rely on plain text input fields for parameters. This can lead to configuration errors, typos, and ambiguity when users need to select from a predefined set of values.
I propose adding support for Radio Buttons and Dropdown Lists (Select) for workflow parameters in the Dagu UI, similar to the form pattern shown below (but also able to provide descriptions per PARAMS as shown in picture):
Visual Reference
The requested feature would allow users to define parameters that render as:
Radio Buttons: For single-choice selection from a short list (e.g., compute location, type).
Dropdowns: For single-choice selection from a longer list.
Example Use Case
Current Behavior: A user must manually type a value like us-east-1 or private into a text input. This risks typos (e.g., us-east-1 vs us-east-1 ) and doesn't enforce valid options.
Proposed Behavior: The workflow definition would support a ui or control schema that maps to specific UI elements.
Radio Buttons:
Label: Which compute location?
Options: [ us-east-1 ] [ us-west-2 ] [ eu-central-1 ]
Selection: User clicks one; the value is set.
Dropdown/Select:
Label: backend
Options: [ http://10.0.1.1:80 ] [ https://10.1.0.1:443 ]