Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Separate process "id" and display-name in config #135

Open
legobeat opened this issue Jun 4, 2024 · 1 comment
Open

[Feature] Separate process "id" and display-name in config #135

legobeat opened this issue Jun 4, 2024 · 1 comment

Comments

@legobeat
Copy link

legobeat commented Jun 4, 2024

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:

procs:
  - label: 'foo [1]'
    shell: 'run-job foo'
  - label: 'foo [2]'
    shell: 'run-job foo'

(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)

@legobeat legobeat changed the title [Feature] Separate process "id" and name in config [Feature] Separate process "id" and display-name in config Jun 4, 2024
@pvolok
Copy link
Owner

pvolok commented Jun 5, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants