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
I stumbled upon a weird situation, where I use getFieldState on a field that uses a custom component, and uses yup to validate which has a required() attached to it. It correctly gives an error object with the text that it is required, but its type is 'optionality' instead of the expected 'required'.
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
Uh oh!
There was an error while loading. Please reload this page.
-
I stumbled upon a weird situation, where I use getFieldState on a field that uses a custom component, and uses yup to validate which has a required() attached to it. It correctly gives an error object with the text that it is required, but its type is 'optionality' instead of the expected 'required'.
Any ideas why this happens?
Beta Was this translation helpful? Give feedback.
All reactions