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
There is an inconsistency if we need a Text input and Check box to be mandatory fields(required).
For Check box there is a required:boolean prop (If true, the checkbox will change its appearence, showing that the value is required.)
For Text Input it is missing such a prop required. There is an optional: boolean prop (If false, will be considered required )
The 2 types of fields look really different and inconsistent: the Check box has a red asterisk and the Text Input has not(if optional=false).
Expected behavior
Unify the look of the 2 components if the field is required(mandatory).
The text was updated successfully, but these errors were encountered:
You are totally right, these two systems shouldn't be living at the same time.
We are planing a redesign for the checkbox component which includes replacing required with optional. But this redesign won't happen at least for some months. @aweell do you think we can bring the optional functionality now (before the redesign)?
100% on this, we can split the redesign into two stages, prioritize making a quick fix to the required prop in order to keep consistency, and then allocate the rest of the epic tasks in another release.
There is an inconsistency if we need a Text input and Check box to be mandatory fields(required).
For Check box there is a required:boolean prop (If true, the checkbox will change its appearence, showing that the value is required.)
For Text Input it is missing such a prop required. There is an optional: boolean prop (If false, will be considered required )
The 2 types of fields look really different and inconsistent: the Check box has a red asterisk and the Text Input has not(if optional=false).
Expected behavior
Unify the look of the 2 components if the field is required(mandatory).
The text was updated successfully, but these errors were encountered: