fix: explicitly set DB option to suppress deprecation warning #421
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
The value we set is the current default for Mongoose 6, but the default will change to false in Mongoose 7. Therefore the warning was popping up. The more conservative option is false, meaning invalid query parameters do NOT result in entire collections getting returned. Refs: HID-2395
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.
The value we set is the current default for Mongoose 6, but the default will change to false in Mongoose 7. Therefore the warning was popping up.
The more conservative option is false, meaning invalid query parameters do NOT result in entire collections getting returned.
Refs: HID-2395