feat!: improve google maps integration#191
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…to feat/google-map-improvements
| - $5 per 1000 loads for the Geocoding API | ||
| - $2 per 1000 loads for the Static Maps API | ||
| - $2 per 1000 loads for the Static Maps API - You can avoid providing a `placeholder` slot. | ||
| - $5 per 1000 loads for the Geocoding API - You can avoid this by providing a `google.maps.LatLng` object instead of a string for the `center` prop |
Contributor
There was a problem hiding this comment.
nit: can we link to the source, where the amounts are coming from?
This might get outdated as time goes by, maybe we could add a disclaimer along the lines: "The example cost is based on this source. Actual cost may change. For more accurate cost estimation, please visit ... "
Closed
zizzfizzix
pushed a commit
to zizzfizzix/nuxt-scripts
that referenced
this pull request
Mar 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
markersprop(string | AdvancedMapMarkerOptions)[]Customize the markers displayed on the static map and the interactive map. Fully reactive.
centerMarkerpropbooleanControls whether a marker is placed at the
centerposition.optionsis renamed tomapOptionsqueryis renamed tocenter, it's now recommended to use{longitude},{latitude}rather than a text query.<script lang="ts" setup> const maps = ref() onMounted(() => { - maps.value // google maps instance + maps.value // { googleMaps, map, createAdvancedMapMarker, resolveQueryToLatLang, importLibrary } }) </script> <template> <ScriptGoogleMap ref="maps" /> </template>