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
{{ message }}
This repository has been archived by the owner on Mar 27, 2023. It is now read-only.
Following up a conversation on Slack, I would like to request the ability to design nested controls as such:
At CloudHealth, we have a lot of form controls following this format, often having to select an option and provide 1 or 2 settings for that option. We are currently converting our platform to Clarity and encountering a lot of those patterns. Some definitely need rethinking the page/form, but in many cases it makes sense UX wise.
I was hoping that the current components would let us do something like this, but each attempt had one small thing preventing it. I’ve been trying all sorts of combinations using helper components such as CdsInputGroup and CdsControl but so far haven’t been able to make the input even just show up at all.
In a nutshell, to produce the mock above, that third row cannot be a CdsControl because that will only let me use 1 control (vs. 2: checkbox + input), and it cannot be a CdsInputGroup (which lets me have more than 1 control) because the CdsCheckboxGroup only fills slots with cds-control elements while the CdsInputGroup is a cds-control-group).
Would you be open to consider this in Clarity Core?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Following up a conversation on Slack, I would like to request the ability to design nested controls as such:
At CloudHealth, we have a lot of form controls following this format, often having to select an option and provide 1 or 2 settings for that option. We are currently converting our platform to Clarity and encountering a lot of those patterns. Some definitely need rethinking the page/form, but in many cases it makes sense UX wise.
I was hoping that the current components would let us do something like this, but each attempt had one small thing preventing it. I’ve been trying all sorts of combinations using helper components such as
CdsInputGroup
andCdsControl
but so far haven’t been able to make the input even just show up at all.In a nutshell, to produce the mock above, that third row cannot be a
CdsControl
because that will only let me use 1 control (vs. 2: checkbox + input), and it cannot be aCdsInputGroup
(which lets me have more than 1 control) because theCdsCheckboxGroup
only fills slots withcds-control
elements while theCdsInputGroup
is acds-control-group
).Would you be open to consider this in Clarity Core?
Beta Was this translation helpful? Give feedback.
All reactions