-
Notifications
You must be signed in to change notification settings - Fork 881
Conditional parameters #11275
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
Comments
Indeed this would a a great UX improvement. I have a few suggestions/questions,
How would this work with CLI?
A checkbox would work better here. |
I like the idea, but @matifali raised a good question, how does it work for CLI users? |
I think we could pass parameter/value config as JSON through the CLI. This would support both multi-select and conditional/nested parameters as some customers have requested.
The show/hide use case would just mean that parameter A is dependent on the config of parameter B, if the validation fails then we throw an error. |
coder_parameter
lacks configurability (conditional parameters)
Update: we're revisiting |
Update again: We're rolling this into a larger "Magic Parameters" effort that will ship in Q1 2025. |
Problem statement
Many customers frequently send in requests to extend the capability of
coder_parameter
s in the UI. There are a few desired features:Proposal
Before we attempt to implement these features individually, @kylecarbs recommended we experiment with allowing users to express
coder_parameter
s as code using JSONForms.We would allow users to write their workspace parameters in the UI using JSONForms and render them using the React integration. In this scenario, the visual and functional flexibility of
coder_parameter
would both be dramatically improved.Note that this is not an explicit feature request. Someone who is interested in tinkering with this can experiment and help decide whether or not it's a viable option.
The text was updated successfully, but these errors were encountered: