findAndModify now returns T | null instead of T | undefined #397
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.
According to the Official document of mongoDB, findAndModify returns the document or null.
I test this problem by below code:
I've confirmed that the result is a pre-updated document if the document matches
{ name: 'abc' }
found, if not, the result is certainly null.Maybe, the return type should be
Promise<T | null>
.Last but not least, I apologize if there are any mistakes in my English writing. I am just Japanese student learning English ;)