fix: ParseFile id creation should be consistent to ensure proper hashing #83
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
generation ofid
is not constant, which could produce multiple file saves.ParseFile
also isn'tIdentifiable
requiring extra work to use in SwiftUI.Approach
id
generation of aParseFile
consistent so when the developer attempts to save multiple versions of the same file, the file is only saved once and replaced for other instances to reduce network callsParseFile
Identifiable
TODOs before merging