Skip to content

array operations not available in ParseObject before save #34

@jegesh

Description

@jegesh

After diving into the code I saw that this was intentional, although the logic escapes me. I'm not interested in saving objects until the user decides he wants to keep them - otherwise I have to detect if he backed out of a form or something and delete the incomplete object. Doesn't it make more sense that array operations should behave the same as any other operation? Is there some obstacle that prevents a straightforward implementation of this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions