-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(NODE-4548): export ChangeStream class from top-level #3357
Conversation
33b6624
to
070b607
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain why the raw user options need to be exposed? (Also, this is more of a "feat" because of the change stream class being newly exposed)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be a feat
like Daria mentioned, and can we update the ticket description as well to reflect that you no longer are exporting the user options?
485e4fe
to
4ba9e2d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed the use in the legacy client, here: mongodb-js/nodejs-mongodb-legacy#1 so this should be ready to go
@@ -1610,13 +1610,13 @@ export class Collection<TSchema extends Document = Document> { | |||
* Updates documents. | |||
* | |||
* @deprecated use updateOne, updateMany or bulkWrite | |||
* @param selector - The selector for the update operation. | |||
* @param filter - The filter for the update operation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for changing these to our spec language.
Description
What is changing?
NODE-4548
We need to make ChangeStream accessible
(Also cleaned up inconsistent naming in deprecated APIs)
What is the motivation for this change?
Backwards compat.
Double check the following
npm run check:lint
script<type>(NODE-xxxx)<!>: <description>