Description
Extracted from: #5574 (comment)
We'd like to improve the UX of rich parameters to be more consistent.
Ideas:
- Make the edit workspace form look the same as the create workspace form.
- Mutable/immutable headers seem odd.
- "Danger zone" around immutables, like img.
- Explain what it means in a description/subtitle in the form.
Original post
can we make the edit workspace form look the same as the create workspace form?
like in v1
and just disable the fields that can't change
also the mutable/immutable headers seem odd to me, it'd be nice if users could define their own sections and we just relied on the yellow text that says it can't be changed instead
What’s friendlier language we can use instead of “mutable” and “immutable” in the form? I also second Dean’s point. It would be cool if we could reuse the form and show the immutable params as disabled forms so the user is still aware of them. I also think it would be nice if we had a box around the immutable parameters like: https://i.imgur.com/tQ0TOhf.png.
i feel like immutable is pretty friendly as code
As a section title it’s probably fine since it maps to configuration. We should at least explain what it means in a description / subtitle in the form.