fix(model+query): make findOne(null), find(null), etc. throw an error instead of returning first doc
#15019
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
…rror instead of returning first doc Re: #14948
hasezoey
approved these changes
Nov 6, 2024
AbdelrahmanHafez
approved these changes
Nov 7, 2024
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.
Re: #14948
Summary
As we found out in #14948,
findOne(null)throws an error with the MongoDB Node driver, but Mongoose treats it asfindOne({}). I do think that makingfindOne(null)andfindOne(undefined)throw an error is more correct (while still allowingfindOne({})andfindOne()to return the first doc), and I think this change is a step in the right direction, but I'm wondering if we should put this in a minor release 8.10, or hold off until 9.0?Examples