I mean that we don't want the messages to appear just because the user has
clicked into the field and then on something else.

Currently the messages appear when the field is touched and invalid.

We want it to be when dirty and invalid instead.

Can this be done through configuration?
On 22 Nov 2014 22:12, "Matt DeKrey" notifications@github.com wrote:

I believe this is handled in the library as-written, unless you're
suggesting after the submit button is pressed. If that is the case, I'd
recommend currently to use a data-val-if to test if the model is different
from your default value.

If I'm wrong, or you have a suggestion for providing the default pristine
value, could you provide a gist?

Thanks!

—
Reply to this email directly or view it on GitHub

Hiding validation messages for "pristine" fields #2

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions