@expofp/floorplan/dist/esm/utils/heatmap-enabled.d.ts

Interactive floor plan library for expos and events

import { type Heatmap } from '@expofp/schema';
/**
 * Does a `config.heatmap` node engage heatmap mode? Presence implies intent:
 * any non-empty node engages unless switched off with an explicit
 * `enabled: false` — so `?heatmap[variant]=yah` alone is enough, and a URL's
 * `?heatmap[enabled]=false` can veto a manifest-set node (config layers
 * replace the node wholesale). One predicate for both consumers — the data
 * loader's fetch decision and the dispatch's mode engagement — so the rule
 * cannot drift. The legacy `?heatmap=true` params are NOT this node: they stay
 * a legacy-URL one-shot and a raw read in the loader.
 */
export declare function heatmapEnabled(heatmap: Heatmap): boolean;
//# sourceMappingURL=heatmap-enabled.d.ts.map