feat(NODE-4789): support Map stringification in EJSON #567
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
W-A-James changed the title 
addaleax reviewed Mar 14, 2023
Co-authored-by: Anna Henningsen <anna@addaleax.net>
nbbeeken added the Primary Review 
nbbeeken suggested changes Mar 15, 2023
Co-authored-by: Neal Beeken <neal.beeken@mongodb.com>
nbbeeken approved these changes Mar 15, 2023
nbbeeken added Team Review 
baileympearson approved these changes Mar 16, 2023
nbbeeken changed the title 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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?
Allow for
Maps to be stringified usingEJSON.stringifyIs there new documentation needed for these changes?
No
Double check the following
npm run lintscripttype(NODE-xxxx)[!]: descriptionfeat(NODE-1234)!: rewriting everything in coffeescript