-
-
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
beforeSave renders Relation column on object invalid on response.success() #1714
Closed
3 tasks done
Comments
This was referenced Apr 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Check out this issue for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!
For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities. For database migration help, please file a bug report.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
Environment Setup
using:
"parse": "~1.8.0",
"parse-server": "2.2.7"
I had the bug filed here parse-community/Parse-SDK-iOS-OSX#911
but I see now this is more of a bug in the cloud-code part of parse-server.
Steps to reproduce
Apparently the problem occurs when a
beforeSave
cloud function returnsresponse.success()
instead ofresponse.success(request.object)
. When using the former on an object that contains aPFRelation
, thatPFRelation
get's screwed up on the client side (becomesPFRelationOperation
).Unfortunately just using response.success(request.object) is not the solution. Using this will keep the
PFRelation
field intact but it will not save any data defined in the cloud function beforeSave method.Here
MyObject
will not save (or create) the 'colorstring' column.Here
MyObject
will save (or create) the 'colorstring' column and it will show up on the dashboard. But will render anyPFRelation
column onMyObject
useless.this issue seems to be similar: #1606
Logs/Trace
The text was updated successfully, but these errors were encountered: