-
Notifications
You must be signed in to change notification settings - Fork 1.8k
test(NODE-4059): Change Stream test typescripting and unified builder fixes #3224
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
Conversation
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.
In change_stream.test.ts there are some TODOs without Jira tickets linked. Otherwise, changes look good
@@ -1,18 +1,17 @@ | |||
'use strict'; | |||
import { expect } from 'chai'; | |||
import * as path from 'path'; |
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.
This is entirely unrelated to your PR but this is something I've wondered. I see we sometimes use import * as path from 'path'
but we don't import other NodeJS modules the same way. Is there a reason we don't destructure path specifically?
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.
I prefer doing this for path beacuse join
is such a genericly named function, so path.join
is more indicative of the functionality. It's not like we have many joins runnning around though.
const dbName = 'changestream_integration_test'; | ||
const collectionName = 'test'; | ||
|
||
// TODO remove withClient and withChangeStream usage, use mocha hooks |
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.
Do we have a jira ticket to go with this TODO? Otherwise, can we create one?
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.
done, NODE-2764
fullDocument: 'updateLookup', | ||
// @ts-expect-error: NODE-XXXX is this a type bug? requires locale |
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.
did you mean to link https://jira.mongodb.org/browse/NODE-4081?
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.
I looked it up this was just incorrect usage, you need to pass in a locale
Description
What is changing?
Break out of test changes for #3191
Is there new documentation needed for these changes?
What is the motivation for this change?
Double check the following
npm run check:lint
script<type>(NODE-xxxx)<!>: <description>