-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v8] Documentation #2471
[v8] Documentation #2471
Conversation
|
||
Note: props in this section are not reactive. They are only used once when the Map instance is constructed. | ||
|
||
#### `mapLib`: any {#maplib} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to confirm, this prop still exists?
Is there any type inference from its value?
I'm looking at Hubble.gl right now as an example of a library compatible with both maplibre and mapbox, so I'll be looking at how common types flow into the maps.
I don't think libs should use mapLib
(instead, use either top-level Map component).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Users can still use mapLib
to control how they include the base map library:
- In the same bundle (
import maplibregl from 'maplibre-gl'
thenmapLib={maplibregl}
) - Split bundle (
mapLib={import('maplibre-gl')}
) - Script tag (
mapLib={window.maplibregl}
)
Split API reference into separate sections for Mapbox and Maplibre