fix: advanced marker position can be null #903
Draft
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.
Fixes #902 🦕
Currently there is still a problem with the tests.
As google.maps.Markers and google.maps.marker.AdvancedMarkerElement are inconsistent in their way of handling the position.
.getPosition
on google.maps.Marker returns a LatLng(lat=0, lng=0) even if no position was provided.While google.maps.marker.AdvancedMarkerElement .position really is
null
.If a fix like the one provided in the PR would be accepted, the tests needs to be changed because of the inconsistency.