-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add Cloud Code triggers Parse.Cloud.beforeFind(Parse.File)
and Parse.Cloud.afterFind(Parse.File)
#8700
Conversation
I will reformat the title to use the proper commit message syntax. |
🚀 Thanks for opening this pull request! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## alpha #8700 +/- ##
==========================================
+ Coverage 93.10% 93.12% +0.01%
==========================================
Files 187 187
Lines 15016 15037 +21
==========================================
+ Hits 13981 14003 +22
+ Misses 1035 1034 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Unfortunately, as browsers do not pass headers in when using an So, I think this implementation is a good start. |
Signed-off-by: Manuel <[email protected]>
Signed-off-by: Manuel <[email protected]>
Parse.Cloud.beforeFind(Parse.File)
and Parse.Cloud.afterFind(Parse.File)
Docs: parse-community/docs#960 |
# [8.1.0-alpha.2](8.1.0-alpha.1...8.1.0-alpha.2) (2025-03-27) ### Features * Add Cloud Code triggers `Parse.Cloud.beforeFind(Parse.File)`and `Parse.Cloud.afterFind(Parse.File)` ([#8700](#8700)) ([b2beaa8](b2beaa8))
🎉 This change has been released in version 8.1.0-alpha.2 |
Pull Request
Issue
Currently, there are no find triggers for files.
Closes: #8241
Closes: #6572
Approach
Tasks