Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
update collection.rst - add cascade_validation opt#3518
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
It makes sense to describe cascade_validation option in collectiondocumentation. `Valid` constraint does not suit all needs, especiallywhen we have to set validation_groups for embed object/forms, and socascade_validation should not be that "hidden".
wouterj commentedJan 28, 2014
👍 This PR is related to issue#2360 |
weaverryan commentedFeb 4, 2014
This is a really great change - the exact types of small changes that make a lot of sense and make the docs really great. So thank you Guillaume! I rebased this against 2.3 (since 2.2 has reached end of life and this patch didn't apply cleanly to 2.3) and opened (and merged) PR#3538. Thanks! |
It makes sense to describe cascade_validation option in collection
documentation.
Validconstraint does not suit all needs, especiallywhen we have to set validation_groups for embed object/forms, and so
cascade_validation should not be that "hidden".