feat: make "current" ParseObjects immutable #266
Merged
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.
New Pull Request Checklist
Issue Description
Currently all objects can be set through current, like: ParseUser.current, ParseInstallation.current, ParseConfig.current. These should be mutable and when the developer wants to mutate, they make mutable copies. This prevents setting to nil directly as current should only happen when using the
logout
method.Related issue: #267
Approach
Make all current properties internally set to the SDK.
All playgrounds examples have shown how to make mutable copies instead of setting
current
directly for some time now. Many people learn how to use the SDK from the Swift playground examples.TODOs before merging
ParseACL