-
Notifications
You must be signed in to change notification settings - Fork 294
Description
Currently in Studio we are using the <Checkbox/> component, rather than the KDS KCheckbox. To standardize user experience and get the benefits of using our design system, we should use the <KCheckbox/> in place of <Checkbox/>
The user should not experience major changes, and all checkboxes should continue to work as they were before
Considerations
It is used 43 times, across 29 files, in Studio. Replacing the components should be fairly straightforward, as there are no additional layers on interconnection or dependencies found while preparing the issue.
The props for KCheckbox are available in the design system documentation, as well as additional information about events and methods.
note:
While making this update, an additional goal/benefit would be to ensure that when converting the component, that the usage of a checkbox at all follows our KDS guidance about when checkboxes are appropriate:
The checkbox is generally used to select one of two possible values in a form. It should not be used to make real-time changes; for this situation, use a KSwitch component instead.
If there are any instances where KSwitch would be better, it would be helpful to either make those changes or create a new issue.