Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Initial validation or initialErrors prop

See original GitHub issue

What if the user has set some field values, and we do store them somewhere, and when the user returns to the app those values are invalid. Is there no way to run validate on initialization?

Issue Analytics

State:
Created 6 years ago
Reactions:22
Comments:50 (13 by maintainers)

Top GitHub Comments

47reactions

anandaroopcommented, Dec 12, 2017

+1 for this use case.

I would like to display validation errors & disable form submission for a record that is already persisted, and will now be newly invalid based on some recent changes in the underlying business logic.

So I would like the initial form load to reflect this, but ran into the same issue where the validator function is not run until some field is touched. This has the effect of leaving the form’s submit button initially enabled for what we consider to be an invalid record.

For now I am working around this by moving logic out of the validator function and into various form components, which seems a shame given all the wins we’ve enjoyed by relying on Formik’s awesome default behavior so far.

10reactions

jaredpalmercommented, Jun 25, 2018

I think initialErrors makes a lot of sense. Feel free to submit a PR. It should be almost identical to initialValues.