docs(validation): add section on global schematype validation, clean up other issues #12466
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…up other issues Fix #12430
hasezoey
approved these changes
Sep 23, 2022
hasezoey
added
the
docs
AbdelrahmanHafez
approved these changes
Sep 23, 2022
Co-authored-by: Hafez <a.hafez852@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #12430
Summary
Some improvements to validation docs. First, add a section highlighting that you can use global schematype configuration to set SchemaType-level validation logic, like adding validation for all number paths or all string paths. I also took some time to add a table of contents and prune some unnecessary details: the
contextoption is no longer supported in Mongoose 6, and no need to specify which versions of Mongoose 4 support$pullvalidation because Mongoose 4 is no longer supported.Examples