-
-
Notifications
You must be signed in to change notification settings - Fork 596
add context to Parse.Object.save #1150
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
Conversation
- context is transmitted as `_context` property in REST request - given that a leading underscore `_` marks a reserved property
Codecov Report
@@ Coverage Diff @@
## master #1150 +/- ##
=======================================
Coverage 92.30% 92.31%
=======================================
Files 54 54
Lines 5235 5241 +6
Branches 1169 1171 +2
=======================================
+ Hits 4832 4838 +6
Misses 403 403
Continue to review full report at Codecov.
|
The context is transmitted as I did not find an existing similar use of internal properties in the REST request, but according to the docs a field name must start with a letter, so there cannot be a conflict with an object property:
So using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quick comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I will try to do a release soon
Thanks! Would be great if you could make a release with parse server release that will merge parse-community/parse-server#6626. |
Exposes the
context
object inParse.Object.save()
so that parameters can be made accessible in Cloud Code triggersbeforeSave
,afterSave
.Example:
Don't merge until