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
Is your feature request related to a problem? Please describe
(Simple Example code at the bottom)
I'm currently using a Form.Control that is validated on any input on change, and wanted to bring both valid and invalid css states to it. I have bound it to a state variable, however to have both vorking I have to bind both IsValid attribute and IsInvalid attribute, although one is just !(negation) of the other.
Describe the solution you'd like
New attribute in Form.Control, that when true applies valid state and invalid when false - maybe add null and undefined to have both still false to allow for UX options and only validating when the developer wants to
Describe alternatives you've considered
Binding both options is still a functional option, although not very developer friendly or well documented.
I'm 100% not the right person to ask that, it has been 3 years since I had this issue and I certainly don't have any ties to the project other than usage
Is your feature request related to a problem? Please describe
(Simple Example code at the bottom)
I'm currently using a Form.Control that is validated on any input on change, and wanted to bring both valid and invalid css states to it. I have bound it to a state variable, however to have both vorking I have to bind both IsValid attribute and IsInvalid attribute, although one is just !(negation) of the other.
Describe the solution you'd like
New attribute in Form.Control, that when true applies valid state and invalid when false - maybe add null and undefined to have both still false to allow for UX options and only validating when the developer wants to
Describe alternatives you've considered
Binding both options is still a functional option, although not very developer friendly or well documented.
Example code:
Proposed attribute (just called it validState, but there are definitely better names out there):
The text was updated successfully, but these errors were encountered: