fix(document): make sure depopulate does not convert hydrated arrays to vanilla arrays #14803
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
One issue that popped up while I was working on #1635 is that
depopulate()
converts Mongoose arrays to vanilla JavaScript arrays. Soband.depopulate('members'); band.members.addToSet(id);
will error out becauseband.members
is no longer a Mongoose array.The approach I came up with is to use
getValue()
: ifgetValue()
returns a Mongoose array, then we just modify the array in-place to avoid triggering setters. If not a Mongoose array, then we have a case where mpath is returning an array of values underneath a document array, like in the #10592 test casedoc.depopulate('docArr.members')
, so we fall back tosetValue()
.I left
assert.ok(!band.embeddedMembers[0].$populated('member'));
commented out because that assertion fails, but I want to look at it some more when we come back to #1635.Examples