fix: ParsePolygon.containsPoint() correctly uses longitude and latitude #116
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
ParsePolygon is encoded/decoded incorrectly with the latitude and longitude being (latitude, longitude) instead of (longitude, latitude).
Approach
Swap the latitude and longitude from (latitude, longitude) to (longitude, latitude). If a developer used ParseSwift <= 5.7.0 to save ParsePolygon's, they will need to update the respective ParseObjects by swapping the latitude and longitude manually.
TODOs before merging