-
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-4877): Add support for useBigInt64 #3519
feat(NODE-4877): Add support for useBigInt64 #3519
Conversation
7f8f32d
to
0125330
Compare
Link to evergreen patch with |
I think the option isn't actually making it to the BSON layer, we "sanitize" the options at the wire protocol layer to make sure that arbitrary options don't reach the bson deserializer, take a look at #2840 |
This PR cannot merge until we do the 5.0 release. |
Can you post an updated link to an evg patch where some errors might just be assertions no longer being equal, that would be expected |
Evergreen patch with |
Lot's of red, unfortunately enough to make it so we can't see the output, atlas connectivity failing though might be a good place to start as that "shouldn't" have been impacted at all. // TODO(NODE-2674): Preserve int64 sent from MongoDB You'll want to look for this comment, likely every spot needs an extra condition to accept bigint |
d330f3f
to
d54383d
Compare
This comment was marked as outdated.
This comment was marked as outdated.
test/integration/node-specific/bson-options/useBigInt64.test.ts
Outdated
Show resolved
Hide resolved
test: function (done) { | ||
var configuration = this.configuration; | ||
var client = configuration.newClient(configuration.writeConcernMax(), { | ||
test: async function () { |
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.
Note for other reviewers these tests are unrelated to the work in the PR and are just changing from callbacks to async/await.
test/integration/node-specific/bson-options/useBigInt64.test.ts
Outdated
Show resolved
Hide resolved
test/integration/node-specific/bson-options/useBigInt64.test.ts
Outdated
Show resolved
Hide resolved
test/integration/node-specific/bson-options/useBigInt64.test.ts
Outdated
Show resolved
Hide resolved
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.
LGTM can't wait to use the biggest of ints!! 🎉
…ptions.promoteValues
test/integration/node-specific/bson-options/useBigInt64.test.ts
Outdated
Show resolved
Hide resolved
test/integration/node-specific/bson-options/useBigInt64.test.ts
Outdated
Show resolved
Hide resolved
test/integration/node-specific/bson-options/useBigInt64.test.ts
Outdated
Show resolved
Hide resolved
@@ -0,0 +1,234 @@ | |||
import { expect } from 'chai'; |
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 file should use snake case (use_bigint_64.test.ts
) or something similar to follow our existing filenaming convention.
test/integration/node-specific/bson-options/useBigInt64.test.ts
Outdated
Show resolved
Hide resolved
Co-authored-by: Bailey Pearson <[email protected]>
Description
Add support for BSON's
useBigInt64
flag to the driverWhat is changing?
useBigInt64
flag is now a part of theBSONSerializationOptions
interfaceuseBigInt64
flag is now therefore part of all implementers of this interfaceIs there new documentation needed for these changes?
No
What is the motivation for this change?
Double check the following
npm run check:lint
scripttype(NODE-xxxx)[!]: description
feat(NODE-1234)!: rewriting everything in coffeescript
applyCommonQueryOptions
function