-
-
Notifications
You must be signed in to change notification settings - Fork 70
feat: add ParseObjectMutable protocol #270
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
Merged
Merged
Changes from 2 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
a470285
• Updatable
vdkdamian ae2a05a
Requested changes
vdkdamian 6bab7b9
Merge branch 'main' into updatable
cbaker6 170cab2
Requested changes + Line length
vdkdamian a7f6d99
Requested changes
vdkdamian 6b21e28
Requested changes
vdkdamian File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,76 @@ | ||
| // | ||
| // ParseObjectMutable.swift | ||
| // ParseSwift | ||
| // | ||
| // Created by Damian Van de Kauter on 30/10/2021. | ||
| // Copyright © 2021 Parse Community. All rights reserved. | ||
| // | ||
|
|
||
| import Foundation | ||
|
|
||
| /** | ||
| The **ParseObjectMutable** protocol adds an empty version of the respective object. This can be used when you only need to update a | ||
cbaker6 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| a subset of the fields of an object as oppose to updating every field of an object. Using an empty object and updating | ||
| a subset of the fields reduces the amount of data sent between client and server when using `save` and `saveAll` | ||
| to update objects. | ||
|
|
||
| **Example use case:** | ||
| ~~~~ | ||
| var user = User.current?.mutable | ||
| user?.customKey = "newValue" | ||
|
|
||
| do { | ||
| try await user?.save() | ||
| } catch { | ||
| // Handle error | ||
| } | ||
| ~~~~ | ||
|
|
||
| - warning: Using the **ParseObjectMutable** protocol requires the developer to use an **init()** without declaring custom properties. | ||
| You can still use non-optional properties if you add them to your **init()** method and give them a default value. | ||
cbaker6 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| If you need a custom **init()**, you can't use the **ParseObjectMutable** protocol. | ||
| */ | ||
| public protocol ParseObjectMutable: ParseObject { | ||
| init() | ||
|
|
||
| var mutable: Self { get } | ||
| } | ||
|
|
||
| public extension ParseObjectMutable { | ||
|
|
||
| /** | ||
| An empty version of the respective object that allows you to update a | ||
cbaker6 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| a subset of the fields of an object as oppose to updating every field of an object. | ||
| - note: You need to use this to create a mutable copy of your **ParseObject**. | ||
| */ | ||
| var mutable: Self { | ||
| var object = self | ||
cbaker6 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| object.objectId = objectId | ||
| object.createdAt = createdAt | ||
| return object | ||
| } | ||
| } | ||
|
|
||
| /** | ||
| The **ParseInstallationMutable** protocol adds an empty version of the respective object. This can be used when you only need to update a | ||
| a subset of the fields of an object as oppose to updating every field of an object. Using an empty object and updating | ||
| a subset of the fields reduces the amount of data sent between client and server when using `save` and `saveAll` | ||
| to update objects. | ||
|
|
||
| It combines the **ParseInstallation** protocol and the **ParseObjectMutable** protocol. | ||
| */ | ||
| public protocol ParseInstallationMutable: ParseInstallation, ParseObjectMutable { | ||
cbaker6 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| init() | ||
| } | ||
|
|
||
| /** | ||
| The **ParseUserMutable** protocol adds an empty version of the respective object. This can be used when you only need to update a | ||
| a subset of the fields of an object as oppose to updating every field of an object. Using an empty object and updating | ||
| a subset of the fields reduces the amount of data sent between client and server when using `save` and `saveAll` | ||
| to update objects. | ||
|
|
||
| It combines the **ParseUser** protocol and the **ParseObjectMutable** protocol. | ||
| */ | ||
| public protocol ParseUserMutable: ParseUser, ParseObjectMutable { | ||
cbaker6 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| init() | ||
| } | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.