fix(document): avoid triggering setter when initializing Model.prototype.collection
to allow defining collection
as a schema path name
#13968
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 #13956
Summary
Right now get the following error when you try to use
collection
as a schema path name:This PR fixes that, you can now use
collection
as a schema name, albeit still with the "collection
is a reserved schema pathname and may break some functionality." warning.Examples