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.
Not sure if this should be an issue or expected behaviour, but one that I quickly created a test case for and provided a fix for.
Issue
req.query is undefined on afterFind.
Considering afterFind is directly related to the Parse.Query that called it, shouldn't req.query be defined?
Test case:
(Fails on Parse Server 4.3.0)
In my use, I wanted to handle req.objects differently depending on whether the query was an include from another object, or whether the query was an or query on the class.