The module's configuration type.
The type of data passed to show(). Use never for
modules that have no show method.
The module's configuration type.
The type of data passed to show(). Use never for
modules that have no show method.
Removes all handlers for the given event type at once.
To remove a single handler, call the unsubscribe function that on returns instead.
Use off for bulk teardown, for example when unmounting a component that registered
several handlers.
The event type whose handlers should all be cleared. A module takes
'shown-features' only if it has a show method.
Subscribes to config-change events.
The handler receives the module's full current configuration right after any change made
with applyConfig, a module-specific setter or resetConfig.
'config-change'
Receives the module's config, or undefined when the config is cleared.
An unsubscribe function. Call it to remove only this handler, leaving the other handlers for the same event type registered.
Subscribes to shown-features events.
The handler is called right after a module's show() method, or its equivalent, updates
the map with new data. Only modules that have a show method offer it.
'shown-features'
Receives the data that was passed to show().
An unsubscribe function. Call it to remove only this handler, leaving the other handlers for the same event type registered.
Lifecycle event module for map modules.
It offers one API for subscribing to module-level events that aren't tied to user interaction with map features. It supports two event types:
config-change: emitted wheneverapplyConfig,resetConfigor any module-specific setter changes the module's configuration.shown-features: emitted by modules that have ashowmethod, immediately after features are displayed on the map.Each
on()call returns an unsubscribe function, so you can remove individual handlers without clearing the entire listener list.Example