Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using reactive validation #382

Open
dpatte opened this issue May 23, 2018 · 1 comment
Open

using reactive validation #382

dpatte opened this issue May 23, 2018 · 1 comment
Labels

Comments

@dpatte
Copy link

dpatte commented May 23, 2018

I have been using collection2 in my meteor projects since Meteor 1.0, but I have never taken advantage of reactive validation - mostly because I am not sure how to use it.

I presume the idea of reactive validation provides a way of automatically notifying a user of invalid fields in a form, keeping track of entered fields that don't match the schema, and revalidating them as they are fixed, but I'm not sure how I would set that up.

This there a code sample of using reactive validation I can peruse?

Thx

@dpatte
Copy link
Author

dpatte commented May 23, 2018

The main issue is understanding how changes to fields in a form are interpreted as reactive data sources for the validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants