This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
Smallest LatLngBounds when visible region crosses dateline #9747
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.
closes #9687, this PR makes sure that the LatLngBounds returned by VisibleRegion complies to:
To make this possible I had to introduce
LatLngBounds.from
, this method was required to bypass bounds recalculation used in normal circumstances. This method also allows end developers to overwrite default LatLngBounds behaviour.Adding this to the 5.1.3 milestone as implementation wasn't complying to the javadoc.
cc @zugaldia