Skip to content

onchange/validation inconsistent #10

@icodeforlove

Description

@icodeforlove

I would like to know more about why we only revalidate when an error exists?

I forked the project and removed those checks, it now validates on every change:

icodeforlove@77918a7

Is there a reason why we wouldn't want to do this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions