FormItem isTouched requirement unnecessary and hides actual valid errors

I’m current working on a form that uses both inline and form-wide validation. I’m trying to cover all cases of someone using the form and trying to pass validation.

One scenario being, someone who doesn’t fill out the form of required fields, and just presses submit and/or triggers the validateForm() function.

Using the current state of the FormItem component, even though Formik is legitimately passing proper errors, because the FormItem is checking for isTouched, it won’t actually display any of the errors. So the user actually doesn’t know why he can’t submit (even though there are errors)

This needs to be fixed asap imo

[jannikbuschke]

Would enabling the SubmitButton be a solution (or at least workaround) for this case? I.e. you can do <SubmitButton disabled={false} /> (https://codesandbox.io/s/x2941k7vpz) to override the default behavior (SubmitButton is only enabled if form is dirty).

[tiagombrito]

Hello again @jannikbuschke

I agree with what you said. My message was just to let people know that if they are having this issue, they need to add the initial variable as null (altho i remember having some value that was not working, i think it was an empty array, but changing it to a null worked). Also, i’m just taking a guess, but i think this behaviour may be coming from formik and not with formik-antd.