-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Add option to convert Parse.Pointer
in Cloud Function payload
#8634
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
Labels
state:released
Released as stable version
state:released-alpha
Released as alpha version
state:released-beta
Released as beta version
type:bug
Impaired feature or lacking behavior that is likely assumed
Comments
Thanks for opening this issue!
|
Parse.Pointer
in Cloud Function payloadParse.Pointer
in Cloud Function payload
This PR blocks the stable release pipeline of Parse Server; it fixes a breaking change that has been introduced by mistake. |
4 tasks
4 tasks
🎉 This change has been released in version 6.3.0-alpha.3 |
🎉 This change has been released in version 6.4.0-beta.1 |
🎉 This change has been released in version 6.4.0-alpha.1 |
🎉 This change has been released in version 6.4.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
state:released
Released as stable version
state:released-alpha
Released as alpha version
state:released-beta
Released as beta version
type:bug
Impaired feature or lacking behavior that is likely assumed
New Issue Checklist
Issue Description
#8490 was actually a breaking change because it changes the payload in Cloud Functions in a way that a Parse Pointer JSON is converted to a Parse.Pointer instance in the payload, instead of being just a POJO as it used to be previously.
Solution
Add a new Parse Server option that determines whether a pointer should be a POJO (by default), or converted to a
Parse.Pointer
instance.Since #8490 is already in beta, and for simplicity, we'll need a
refactor
PR for both thealpha
andbeta
branch.Environment
Server
6.3.0-beta.1
References
The text was updated successfully, but these errors were encountered: