@tomtom-org/maps-sdk-plugin-agent-toolkit 0.2.6 → 0.2.7

package/dist/index.d.ts

@@ -918,14 +918,13 @@ export declare type PlacesEntry = {
     /** Lazy place-id → boundary polygon index, built on first lookup through PlacesState.getGeometryForPlace. */
     _geometryByPlaceId?: Record<string, PolygonFeature<CommonPlaceProps>>;
     /**
-     * Per-entry display modules. Each entry owns its own PlacesModule per marker theme and a
-     * dedicated GeometriesModule, so display state lives on the entry rather than on a shared
-     * slice-level module. Lazy-initialised via PlacesState helpers — undefined until first show.
+     * Per-entry display modules. An entry is rendered under at most one marker theme at a time,
+     * so a single PlacesModule covers all themes — `_showEntryAs` rethemes it via `applyTheme`.
+     * A dedicated GeometriesModule renders the entry's boundary polygons.
+     * Lazy-initialised via PlacesState helpers — undefined until first show.
      */
     _modules?: {
-        pin?: PlacesModule;
-        baseMap?: PlacesModule;
-        pinClustered?: PlacesModule;
+        places?: PlacesModule;
         geometries?: GeometriesModule;
     };
     /** The marker theme currently rendering this entry, or undefined when hidden. */
@@ -939,10 +938,10 @@ declare type PlacesMarkerType = 'pin' | 'base-map' | 'pin-clustered';
  * State for the places layer: an append-only history of place results plus per-entry display
  * modules.
  *
- * Each entry owns its own PlacesModule (per marker theme: pin / base-map / pin-clustered) and
- * a dedicated GeometriesModule, lazy-initialised on first show. The slice no longer holds
- * shared modules — display state lives on the entry, so two entries can be rendered side by
- * side under different themes without sharing a single source.
+ * Each entry owns a single PlacesModule (rethemed in-place via `applyTheme` when the marker
+ * type changes — an entry only renders under one theme at a time) and a dedicated
+ * GeometriesModule, lazy-initialised on first show. Display state lives on the entry, so two
+ * entries can be rendered side by side under different themes without sharing a single source.
  *
  * @group Agent Toolkit
  */
@@ -966,9 +965,9 @@ declare class PlacesState implements StateSlice {
      */
     setEntryMode(mode: EntryMode): Promise<void>;
     /**
-     * Lazy-init and return the entry's PlacesModule for the given marker theme. Each entry
-     * keeps a separate module per theme so flipping themes for one entry doesn't disturb
-     * another. Throws when the entry id is unknown.
+     * Lazy-init and return the entry's PlacesModule, rethemed to `markerType`. An entry only
+     * ever renders under one theme at a time, so the same module is reused — flipping themes
+     * calls `applyTheme` in place. Throws when the entry id is unknown.
      */
     getEntryPlacesModule(entryId: string, markerType: PlacesMarkerType): Promise<PlacesModule>;
     /**