feat(NODE-4871): Add support for int64 deserialization to BigInt #542
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
nbbeeken suggested changes Dec 15, 2022
W-A-James commented Jan 3, 2023
nbbeeken suggested changes Jan 3, 2023
nbbeeken suggested changes Jan 3, 2023
nbbeeken previously approved these changes Jan 3, 2023
nbbeeken approved these changes Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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 capability to deserialize BSON
LongtoBigIntIs there new documentation needed for these changes?
Yes. Documentation changes in README and inline docs
What is the motivation for this change?
Allow users to make use of native Javascript
BigInts instead ofBSON.LongDouble check the following
npm run check:lintscripttype(NODE-xxxx)[!]: descriptionfeat(NODE-1234)!: rewriting everything in coffeescript