Added optional parameter "addEmptyObject" to keep model consistent #6
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.
The problem when reverse populating a model is that the returned object hierarchy is not consistent.
Example:
Two authors:
{name: "A", _id: 1} , {name: "B", _id: 2}
Two books:
{name: "book1", author: 1}, {name: "book2", author: 1}
Reverse population of authors with books gives you:
[ { name: "A", _id: 1, books: [{name: "book1", author: 1}, {name: "book2", author: 1}] },
{ name: "B", _id: 2} ]
With the new optional argument "addEmptyObject" set to true it gives you:
[ { name: "A", _id: 1, books: [{name: "book1", author: 1}, {name: "book2", author: 1}] },
{ name: "B", _id: 2, books: [] } ]
I.e., the author object is kept consistent (every author has the field books).