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

Add recipes section to the docs #18

Open
busypeoples opened this issue Jun 22, 2017 · 3 comments
Open

Add recipes section to the docs #18

busypeoples opened this issue Jun 22, 2017 · 3 comments

Comments

@busypeoples
Copy link
Owner

Due to the fact that Revalidation doesn't handle every specific case, but rather tries to focus on two things: local state management and synchronous validation, there should be a recipe section explaining how to approach certain situations. See #14 and #15 for example.

@presto2116
Copy link

I really appreciate the work you are doing on this. It is by far the easiest form validation package for react. One situation I am running into is I like the instantValidation, but some of the validation rules don't give the user a chance before warning them of an error I.E. validEmail or isLengthGreaterThan. Is there a way to ValidateAll on submit, and then have instantValidation. Right now I can only get it to work only on Submit, or instantValidation.

@busypeoples
Copy link
Owner Author

Thank you for the feedback!

Just for the info: there is still some development happening with the forms, I think I will be releasing version 0.10 tomorrow. You can keep track via the 0.10 branch.

So if I understand correctly: Validation should only occur when the field has been touched?
Doesn't the first example (Basic) http://revalidation.oss.25th-floor.com/example/demo/ cover the case?
It only validates the field once it's changed and validates all on submit. Or could this be solved via onKeyUpinsteadonChange`? Letting the user finish typing and then validate that field.

Or is there something I'm overseeing here?

@busypeoples
Copy link
Owner Author

Ok, I think I understand the problem. Will think about how to to tackle the problem efficiently.

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

No branches or pull requests

2 participants