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
In a recent pull-request (#2116) were added ability to force trigger/prevent validation when calling setFieldValue and setFieldTouched methods, but this ability is still missing in FieldHelperProps.
Desired Behavior
Need to have ability to force trigger/prevent validation using FieldHelperProps, so interface of this methods will look like:
🚀 Feature request
Current Behavior
In a recent pull-request (#2116) were added ability to force trigger/prevent validation when calling setFieldValue and setFieldTouched methods, but this ability is still missing in FieldHelperProps.
Desired Behavior
Need to have ability to force trigger/prevent validation using FieldHelperProps, so interface of this methods will look like:
setValue(value: any, shouldValidate?: boolean): void
setTouched(value: boolean, shouldValidate?: boolean): void
Suggested Solution
Just pass-through "shouldValidate" argument inside setValue/setTouched method down to the setFieldValue/setFieldTouched method.
Who does this impact? Who is this for?
All users
Describe alternatives you've considered
Now instead of this I forced to use formik context methods (setFieldValue and setFieldTouched) directly, which is a little bit less convinient.
Additional context
-//-
The text was updated successfully, but these errors were encountered: