feat(NODE-3729): add withId to default return type for collection.find and collection.findOne #3039
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.
Description
What is changing?
Adding a
WithId
wrapper to the return type of collection.findOne and collection.findIs there new documentation needed for these changes?
No, should be self documented by ts output and is otherwise (probably) expected behavior
What is the motivation for this change?
Ran into a scenario similar to NODE-3729 and after seeing PR 3020 I wanted to suggest a more targeted solution that only impacts the find methods directly.
By changing only the return type of
.find()
; the_id
property is correctly returned on all find operations. I limited the change to only instances where the return type for.find()
isn't overridden because at that point the user is stating they want manual control over the resulting type and are responsible for their own_id
definition (if one exists).Double check the following
npm run check:lint
script<type>(NODE-xxxx)<!>: <description>