Skip to content

Add option to convert Parse.Pointer in Cloud Function payload #8634

Closed
#8646
Closed
Add option to convert Parse.Pointer in Cloud Function payload#8634
#8646
Labels
state:releasedReleased as stable versionstate:released-alphaReleased as alpha versionstate:released-betaReleased as beta versiontype:bugImpaired feature or lacking behavior that is likely assumed

Description

@mtrezza
mtrezza
opened on Jun 11, 2023

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 the alpha and beta branch.

Environment

Server

  • Parse Server version: 6.3.0-beta.1

References

Activity

  1. parse-github-assistant commented on Jun 11, 2023

    @parse-github-assistant
    parse-github-assistantBot
    on Jun 11, 2023

    Thanks for opening this issue!

    • 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
  2. mtrezza
    changed the title [-]Add temp option to convert `Parse.Pointer` in Cloud Function payload[/-] [+]Add option to convert `Parse.Pointer` in Cloud Function payload[/+] on Jun 11, 2023
  3. mtrezza
    added
    type:bugImpaired feature or lacking behavior that is likely assumed
    block:releaseNeeds to be resolved before next release on release branch; remove label afterwards
    on Jun 11, 2023

  4. mtrezza commented on Jun 12, 2023

    @mtrezza
    mtrezza
    on Jun 12, 2023
    MemberAuthor

    This PR blocks the stable release pipeline of Parse Server; it fixes a breaking change that has been introduced by mistake.

  5. mtrezza
    closed this as completedin #8646on Jun 23, 2023

  6. parseplatformorg commented on Jun 23, 2023

    @parseplatformorg
    parseplatformorg
    on Jun 23, 2023
    Contributor

    🎉 This change has been released in version 6.3.0-alpha.3

  7. parseplatformorg
    added
    state:released-alphaReleased as alpha version
    on Jun 23, 2023

  8. parseplatformorg commented on Sep 16, 2023

    @parseplatformorg
    parseplatformorg
    on Sep 16, 2023
    Contributor

    🎉 This change has been released in version 6.4.0-beta.1

  9. parseplatformorg
    added
    state:released-betaReleased as beta version
    on Sep 16, 2023

  10. parseplatformorg commented on Sep 20, 2023

    @parseplatformorg
    parseplatformorg
    on Sep 20, 2023
    Contributor

    🎉 This change has been released in version 6.4.0-alpha.1

  11. parseplatformorg commented on Nov 16, 2023

    @parseplatformorg
    parseplatformorg
    on Nov 16, 2023
    Contributor

    🎉 This change has been released in version 6.4.0

  12. parseplatformorg
    added
    state:releasedReleased as stable version
    on Nov 16, 2023
  13. mtrezza
    removed
    block:releaseNeeds to be resolved before next release on release branch; remove label afterwards
    on Jan 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    state:releasedReleased as stable versionstate:released-alphaReleased as alpha versionstate:released-betaReleased as beta versiontype:bugImpaired feature or lacking behavior that is likely assumed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions