feat(document): add support for getAtomics() to allow custom container types to utilize atomics
#15817
+45
−3
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.
Summary
Right now, only container types that extend from Mongoose arrays can take advantage of atomics (change tracking so, for example,
push()translates to$pushinsave()). That's problematic for trying to implement custom types like Sets.This PR makes Mongoose look for a
getAtomics()function on values, so custom types can use atomics without having to implement an internal method like$__atomics().Similarly, I added
clearAtomics()which allows Mongoose to clear custom types' atomics after successful saveExamples