fix: some async/await methods won't throw errors #334
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
Async/await methods that have void returns won't throw errors received from the server; particularly
delete()
,logout()
,ParseUser.verif...()
, andParseAnalytics
methods. They would on throw http errors.In addition, some places in the code still force unwrap or can be done with less code.
Related issue: #n/a
Approach
The the returned value of async/await void methods and throw errors if needed.
Remove force unwrapping and clean up code.
TODOs before merging