-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Closed
Labels
type:bugImpaired feature or lacking behavior that is likely assumedImpaired feature or lacking behavior that is likely assumed
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest version of Parse Server.
Issue Description
In latest releases (5.5.5 and 6.2.2) we seem to be unable to determine whether beforeFind is from a Get or a Find. These recent patches ensure that beforeFind is ran for both Find and Get, but there does not seem to be any way to make this distinction? This may break some implementations that relied on such distinction.
Steps to reproduce
Construct a query on Class A with a Parse Pointer relationship to Class B. Log req.isGet inside beforeFind of Class B and observe req.isGet is false
Actual Outcome
req.isGet inside beforeFind seems to return false regardless of whether beforeFind is from a Get or a Find
Expected Outcome
req.isGet to be true in the log described above or an alternative way to make this distinction?
Server
- Parse Server version:
5.5.5 and 6.2.2
Metadata
Metadata
Assignees
Labels
type:bugImpaired feature or lacking behavior that is likely assumedImpaired feature or lacking behavior that is likely assumed