You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The process name is used both as key in the config yaml and as display-name in sidebar.
Would make scripting a lot smoother if this could be separated by introducing a new property for display name.
procs:
foo1:
label: 'foo [1]'
shell: 'run-job foo'
foo2:
label: 'foo [2]'
shell: 'run-job foo'
# still displayed as "bar"
bar:
shell: 'run-job foo'
If neither backwards-compat or the overhead of overloaded config types are major concerns, it would further simplify things to make it a list rather than a dict:
(There are pros/cons to having the "unique ID" aspect of each job having an ID/name, still - not hard to imagine potential future functionality making use of it)
The text was updated successfully, but these errors were encountered:
legobeat
changed the title
[Feature] Separate process "id" and name in config
[Feature] Separate process "id" and display-name in config
Jun 4, 2024
This is definitely a needed feature. In fact I even went to check if I implemented the "title" field, because I thought about it in the past. Turns out it's not implemented yet.
The process name is used both as key in the config yaml and as display-name in sidebar.
Would make scripting a lot smoother if this could be separated by introducing a new property for display name.
If neither backwards-compat or the overhead of overloaded config types are major concerns, it would further simplify things to make it a list rather than a dict:
(There are pros/cons to having the "unique ID" aspect of each job having an ID/name, still - not hard to imagine potential future functionality making use of it)
The text was updated successfully, but these errors were encountered: