fix(schema): avoid propagating toObject.transform
and toJSON.transform
option to implicitly created schemas
#13634
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.
Fix #13599
Summary
#13599 pointed out that we introduced a potentially breaking change in #13396:
transform()
option propagates to implicitly created schemas, which means existingtransform
functions need to account that they'll run on subdocuments. This PR undoes that backwards breaking change by explicitly omittingtransform
from thetoJSON
andtoObject
options propagated down to implicitly created schemas.Examples