Repository navigation
Can setModel optionally set touched? #51
Description
Activity
here's a PR #52
validation runs all the time, it's your preference whether you display errors on touched fields only or not.
It would be helpful if you can discuss the use-case a bit more so that I can replicate it somewhere like codesandbox.io
I've noticed that in the scenario where setModel is being called to populate the form model after an API called, the fields are still deemed 'untouched' and therefore any warnings, errors won't appear since the validation isn't run.
Rather than the application having to call setFieldToTouched for all the relevant fields, it would be handy if setModel did it