Update docs to include the section about populating multiple paths in middleware #11177
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added a section that explains how to populate multiple paths in middleware.
aleksadjukic
changed the title
vkarpov15
requested changes
Jan 6, 2022
| Populating multiple paths in middleware is just a little bit trickier than what you may think. Here's how you may expect it to work: | ||
|
|
||
| ```javascript | ||
| userSchema.pre('find', function (next) { |
There was a problem hiding this comment.
Would be great to add the schema definition to this example: it isn't clear that followers and following reference User
There was a problem hiding this comment.
Agreed, will do :)
vkarpov15
added
the
docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added a section that explains how to populate multiple paths in middleware.
Summary
This is a pretty common use case, yet it is not really straight forward to achieve, so I believe that the solution to the problem should definitely be in the documentation.