fix(query): remove unnecessary check for atomic operators in findOneAndReplace() #13678
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
Co-authored-by: Ostap Skryshevskyi <osskrisha@gmail.com>
disable id virtual if `alias:id` set
fix: timestamps:false on bulkWrite works
fix: setting `flattenObjectIds` returns null doc
AbdelrahmanHafez
approved these changes
Aug 1, 2023
|
Merging into 7.5 👍 |
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.
Summary
This error check is both brittle and unnecessary. Unnecessary because the MongoDB driver already throws
MongoInvalidArgumentError: Replacement document must not contain atomic operators. Brittle because it doesn't take into account chaining, like.findOneAndReplace().set({ $push: 'foo' }). I also don't like how this check uses vanillaErrorrather thanMongooseError.Examples