fix: default cache policy for ParseFile uses SDK default #274
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
ParseFile should use the default cache policy set when initializing the SDK.
Remove
NSObject
comparison fromParseOperation
set as it doesn't work well with nonNSObjects
.Related issue: #n/a
Approach
Switched policy to previous default policy and cleaned up documentation.
TODOs before merging
ParseOperation
set methodParseOperationTests