You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
Are there any plans to add a global option (like those listed at https://mongoosejs.com/docs/api/mongoose.html#mongoose_Mongoose-set) for strictPopulate? I would much prefer such an option instead of setting the more impactful strict option to false for my models, #5124 (comment)
I'm dealing with a older codebase that has many populates and it's very difficult to track down which ones are using paths that don't exist. Also, there is extensive use of the following pattern
Where subPath1 is only defined for a subset of x, y, and z. In my testing, if subPath1 is not defined for x, y, and z the strictPopulate error is thrown.
If a global option is out of the question, could this be added as a schema level option instead (or in addition).
What are the versions of Node.js, Mongoose and MongoDB you are using? Note that "latest" is not a version.
node: 12.15.0
mongoose: 6.0.5
mongo: 4.4.5
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
Are there any plans to add a global option (like those listed at https://mongoosejs.com/docs/api/mongoose.html#mongoose_Mongoose-set) for strictPopulate? I would much prefer such an option instead of setting the more impactful strict option to false for my models, #5124 (comment)
I'm dealing with a older codebase that has many populates and it's very difficult to track down which ones are using paths that don't exist. Also, there is extensive use of the following pattern
Where subPath1 is only defined for a subset of x, y, and z. In my testing, if subPath1 is not defined for x, y, and z the strictPopulate error is thrown.
If a global option is out of the question, could this be added as a schema level option instead (or in addition).
What are the versions of Node.js, Mongoose and MongoDB you are using? Note that "latest" is not a version.
node: 12.15.0
mongoose: 6.0.5
mongo: 4.4.5
The text was updated successfully, but these errors were encountered: