-
-
Notifications
You must be signed in to change notification settings - Fork 71
Open
Labels
bounty:$100Bounty applies for fixing this issue (Parse Bounty Program)Bounty applies for fixing this issue (Parse Bounty Program)type:featureNew feature or improvement of existing featureNew feature or improvement of existing feature
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
While #401 with its PR #406 was a great simplification when updating an object, it still requires special consideration when updating an object.
Specifically:
- A developer still has to keep in mind that there is a special approach with
obj.key.set(\.key, to: "value2")
(see example) needed to only send updated keys to the server, and they cannot simply useobj.key = "value2"
. - The special method
obj.key.set(\.key, to: "value2")
contains a duplication of parameters; it requires a reference tokey
two times.
Feature / Enhancement Description
Further simplify to allow to use obj.key = "value2"
without calling any special method.
Example Use Case
Alternatives / Workarounds
Status quo
References
- Discussion about possible approach: WIP: Strip out unchanged keys on object update #263
Metadata
Metadata
Assignees
Labels
bounty:$100Bounty applies for fixing this issue (Parse Bounty Program)Bounty applies for fixing this issue (Parse Bounty Program)type:featureNew feature or improvement of existing featureNew feature or improvement of existing feature