fix: saving ParseFiles locally do not throw error #399
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
Attempting to fetch or save a file locally that has a directory e.g.
test/file.svg
causes the Swift SDK to throw an error on the client because it attempts to create the directory structure in the filename instead of just taking the filename.Note: This does not fix the issue of saving ParseFiles with directories in their names to the server as that issue appears to be server-side and not interpreting strict JSON.
Related issue: #n/a
Approach
Only use the file name when saving ParseFile's locally and ignore the directories as they are unnecessary.
TODOs before merging