feat!: improve google maps integration #191
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.
π Linked issue
#103
#187
#169
#83
β Type of change
π Description
The current implementation of Google Maps has some issues, this is due to how unclear API boundaries. We need a tighter coupling around shared map and a placeholder props, everything else needs to be exposed to end users so they can implement it themselves.
Docs will still need some work in the future.
π Features
markers
prop(string | AdvancedMapMarkerOptions)[]
Customize the markers displayed on the static map and the interactive map. Fully reactive.
centerMarker
propboolean
Controls whether a marker is placed at the
center
position.options
is renamed tomapOptions
query
is renamed tocenter
, it's now recommended to use{longitude},{latitude}
rather than a text query.