Closed PaulioRandall closed 2 weeks ago
@jamesscottbrown I've just noticed a small issue I introduced in the last commit. Hold off on this one.
@jamesscottbrown I've just noticed a small issue I introduced in the last commit. Hold off on this one.
@jamesscottbrown Good to go.
What does this change?
<Map>
component with TypeScript.map
context in<Map>
tomapStore
.mapCursorStore
context.mapStore
andmapCursorStore
to<Map>
to enable reactivity based map loading.Why?
The way MapLibre uses JavaScript's event system makes it difficult and verbose to manage propagation of events within project specific code. Specifically, ensuring events for top most features take precedence in controlling the state of the map including current popup, highlights, mouse style, or any other map or app state. For example:
mouseenter
event setting the cursor maybe overridden in the same tick by amouseleave
event for a different feature, possible in an unrelated layer. The top most feature should determine the final cursor style.marker
) for the top most feature but we also want to keep popup specific code with its layer definition and isolated from other popups.How is it tested?
Storybook and in live applications.
How is it documented?
Storybook.
Are light and dark themes considered?
No.
Is it complete?
index.js
?