react-listing-engine 0.6.5 → 0.6.6

package/dist/shadcn/index.d.cts

@@ -1,259 +0,0 @@
-import * as react from 'react';
-import { ReactNode } from 'react';
-import { d as IListingCardProps, e as IListingComponents, f as IListingEmptyProps, g as IListingFilterPanelProps, h as IListingLoadingProps, i as IListingMarkerProps, j as IListingPopupProps, k as IListingResultHeaderProps, l as IListingSearchProps, m as IListingSidebarProps, a as IListingToolbarProps, D as DatasetDefinition, F as FilterRegistry, I as IListingConfigOptions } from '../components-provider-FinfaqUT.cjs';
-import { L as LatLng, a as MapProvider } from '../map-provider.interface-DT-v1plm.cjs';
-import { U as UrlSyncController } from '../url-sync.controller-DXSIWgTa.cjs';
-import { ClassValue } from 'clsx';
-
-/**
- * Convenience wrapper around `ListingComponentsProvider` that wires in every
- * package-shipped `Default*` component (via `shadcnDefaultComponents`, the
- * shared source of truth also used by `ListingApp`'s merge). Use this if you
- * want the styled adapter out of the box; use `ListingComponentsProvider`
- * directly (with your own components for some or all slots) otherwise -- the
- * two compose fine since `ListingComponentsProvider` falls back per-slot.
- * Mirrors `react-wizard-engine`'s `WizardComponentsProviderWithDefaults`.
- */
-declare function ListingComponentsProviderWithDefaults({ children }: {
-    children: ReactNode;
-}): react.JSX.Element;
-
-/**
- * Default styled `Card` slot. Renders an optional image, title, subtitle,
- * price and badge from a plain view-model item, and doubles as the
- * clickable/selectable surface (`onSelect`) -- when `onSelect` is provided
- * the card is a `button` rather than a `div` + click handler so it is
- * keyboard operable and announces as a toggle (`aria-pressed`) for free.
- * When `onSelect` is absent (display-only usage) it renders as a
- * non-interactive `<article>` with the same visual classes, minus the
- * button/focus/aria-pressed semantics -- so a purely presentational card
- * doesn't add a no-op tab stop.
- */
-declare function DefaultCard({ item, selected, onSelect }: IListingCardProps): react.JSX.Element;
-
-/**
- * Every `/shadcn` styled default, keyed by slot -- the single source of truth
- * both `ListingComponentsProviderWithDefaults` (spreads it verbatim) and
- * `ListingApp` (spreads a `components` override OVER it) build on.
- *
- * Kept as a plain object, not JSX, so a caller can merge it with
- * `{ ...shadcnDefaultComponents, ...overrides }` and hand the result to ONE
- * `ListingComponentsProvider`. This matters because `ListingComponentsProvider`
- * merges `provided ?? ITS OWN private, UNSTYLED fallbacks` per slot -- it does
- * not read the parent context (see `src/react/components-provider.tsx`).
- * Nesting a `ListingComponentsProvider` (with only the overrides) INSIDE a
- * `ListingComponentsProviderWithDefaults` would therefore silently reset
- * every un-overridden slot back to the bare fallback instead of the shadcn
- * default -- exactly the bug this object exists to avoid.
- */
-declare const shadcnDefaultComponents: IListingComponents;
-
-/** Default styled `Empty` slot: a centered empty state with an icon, heading and hint. */
-declare function DefaultEmpty(_props: IListingEmptyProps): react.JSX.Element;
-
-/** Default styled `FilterPanel` slot: stacks one filter control per row inside `Sidebar`. */
-declare function DefaultFilterPanel({ children }: IListingFilterPanelProps): react.JSX.Element;
-
-/** Default styled `Loading` slot: a shimmering skeleton list, announced via `role="status"`. */
-declare function DefaultLoading(_props: IListingLoadingProps): react.JSX.Element;
-
-/** Default styled `Marker` slot: a small price pill for a map point. */
-declare function DefaultMarker({ point }: IListingMarkerProps): react.JSX.Element;
-
-/**
- * Default styled `Popup` slot: a small card with an accessible close button.
- * `role="group"` + `aria-label` (rather than `role="dialog"`) since this is a
- * non-modal, non-focus-trapped popup anchored to a map marker -- `dialog`
- * without modality/focus management would misrepresent it to AT users.
- */
-declare function DefaultPopup({ entity, onClose }: IListingPopupProps): react.JSX.Element;
-
-/** Default styled `ResultHeader` slot: `"{count} results"`, or `"{count} of {total} results"` when a distinct total is known. */
-declare function DefaultResultHeader({ count, total }: IListingResultHeaderProps): react.JSX.Element;
-
-/** Default styled `Search` slot: a plain styled text input. */
-declare function DefaultSearch({ value, onChange, placeholder }: IListingSearchProps): react.JSX.Element;
-
-/**
- * Default styled `Sidebar` slot: the outer chrome for the filters column in
- * `ListingLayout`. Full width and unbordered on mobile (stacks above the
- * results in normal document flow); becomes a fixed-width bordered rail from
- * `md` up.
- */
-declare function DefaultSidebar({ children }: IListingSidebarProps): react.JSX.Element;
-
-/** Default styled `Toolbar` slot: a bordered bar wrapping arbitrary children. */
-declare function DefaultToolbar({ children }: IListingToolbarProps): react.JSX.Element;
-
-interface IListingLayoutProps {
-    /**
-     * Optional search box, wired by the CONSUMER into their own `TFilters`
-     * shape. `ListingLayout` is filters-shape-erased (same reasoning as the
-     * engine itself -- see `ListingEngineOptions`'s docstring) so it cannot
-     * derive a generic "search" filter on its own; when omitted, no search box
-     * is rendered at all. Documented, deliberate scope: wiring a named
-     * "search" filter convention end-to-end is a future enhancement.
-     */
-    search?: {
-        value: string;
-        onChange: (value: string) => void;
-        placeholder?: string;
-    };
-    className?: string;
-    /** Extra content rendered at the end of the filter bar, alongside `ListingResultHeader` (e.g. a sort control). */
-    toolbarEnd?: ReactNode;
-    /**
-     * Whether `ListingLayout` fetches the first page itself on mount
-     * (`engine.applyFilters({})`). Defaults to `true` (batteries-included).
-     * Pass `false` to defer the initial fetch to the caller -- e.g. a
-     * search-before-results flow, or when `urlSync` hydrates filters from the
-     * URL and should drive the first fetch instead of racing it.
-     */
-    autoFetch?: boolean;
-    /**
-     * Forwarded verbatim to `<ListingMap center={mapCenter} />`. Omit to get
-     * `ListingMap`'s turnkey auto-fit default (frames the map to its own data
-     * once it loads) -- passing `mapCenter` opts OUT of auto-fit entirely, on
-     * the theory that an explicit initial view is a deliberate choice
-     * (see `ListingMap`'s doc comment's "Auto-fit" section).
-     */
-    mapCenter?: LatLng;
-    /** Forwarded verbatim to `<ListingMap zoom={mapZoom} />`. See `mapCenter`. */
-    mapZoom?: number;
-}
-/**
- * Full, responsive default listing experience, matching the "top filter bar
- * + list-left/map-right split" pattern of a typical `/find` real-estate
- * search page: a sticky horizontal filter bar (search + filter groups +
- * result count), then below it a split -- a scrollable card grid on the left
- * and a full-height map on the right. Composed entirely from the
- * structure-only compound components in `~/react` plus the injected slot
- * components (via `useListingComponents()` for `Search`, and implicitly
- * through each compound component for `Card`/`Empty`/`Loading`/etc.) -- this
- * file adds layout/chrome only, no new business logic.
- *
- * Layout choices (documented, not the only valid ones):
- * - FILTER BAR (`data-slot="listing-layout-filter-bar"`): `sticky top-0`,
- *   `border-b`/`bg-background`, and a `flex flex-wrap items-end gap-3` row
- *   containing the injected `Search` (when `search` is passed),
- *   `<ListingFilters>` (given the same horizontal row className plus a
- *   `min-w-0` `groupClassName` so individual groups can shrink instead of
- *   forcing overflow), and a trailing `ml-auto` cluster with
- *   `<ListingResultHeader>` + `toolbarEnd`. `flex-wrap` is what makes this
- *   gracefully reflow on narrow widths -- groups drop to new lines instead
- *   of overflowing or requiring a separate mobile-only layout.
- * - SPLIT (`data-slot="listing-layout-split"`): a single CSS grid,
- *   `md:grid-cols-[minmax(340px,42%)_1fr]` from `md` up (list column floors
- *   at 340px, caps at 42% of the split's width; map takes the rest). Below
- *   `md` there is no grid -- just two full-width panels, and exactly one is
- *   visible at a time (see the mobile toggle below).
- * - LIST region (`data-slot="listing-layout-list"`): `overflow-y-auto`, its
- *   own scroll container so browsing the list never requires scrolling the
- *   map out of view. Holds `<ListingList>` (an auto-fill card grid) and
- *   `<ListingPagination>`.
- * - MAP region (`data-slot="listing-layout-map"`): fills the split's full
- *   height via the grid's default stretch alignment (no explicit height
- *   needed), plus `md:sticky md:top-0` so that if a consuming app ever lets
- *   `ListingLayout` sit inside a naturally document-scrolling page (rather
- *   than the fixed-height shell this component defaults to via
- *   `h-full min-h-0`), the map still pins in place while the list scrolls
- *   past -- inert (but harmless) in the default fixed-height composition,
- *   where there is nothing above the split to scroll past in the first
- *   place. Renders `<ListingMap>` with a default centered fallback message
- *   (`MAP_FALLBACK`) for when no `MapProvider` is configured, so the pane
- *   never looks broken/blank.
- * - MOBILE LIST/MAP TOGGLE (`data-slot="listing-layout-mobile-toggle"`,
- *   `md:hidden`): a small two-button segmented control, local `useState`
- *   (`mobileView`), defaulting to `'list'`. Both the list and map regions
- *   stay mounted at all times (never remounted on toggle -- that would
- *   re-trigger `ListingList`'s/`ListingMap`'s own mount effects for no
- *   reason); only their visibility flips via `hidden md:block` /
- *   `block md:block`, i.e. the toggle only ever matters below `md` -- at
- *   `md` and up both regions are always visible side by side and the toggle
- *   control itself is hidden.
- * - Fetches the first page itself on mount (`engine.applyFilters({})`) by
- *   default: none of the structure-only `~/react` compound components do
- *   this (they are deliberately side-effect-free), so as the
- *   batteries-included "full experience" entry point, `ListingLayout` is the
- *   natural, single owner of that one bootstrapping side effect. Pass
- *   `autoFetch={false}` to opt out and drive the first fetch yourself (e.g.
- *   search-before-results, or when `urlSync` hydrates filters from the URL).
- */
-declare function ListingLayout({ search, className, toolbarEnd, autoFetch, mapCenter, mapZoom, }: IListingLayoutProps): react.JSX.Element;
-
-/**
- * `ListingApp.map` accepts either a ready-made `MapProvider` (any
- * implementation -- Google, a fake, a future provider) or, as a convenience,
- * a bare Google Maps API key. See `useResolvedMap`'s doc comment for why the
- * key shorthand is resolved via a dynamic `import()` rather than a static one.
- *
- * Both shapes optionally carry `center`/`zoom` -- the initial view, forwarded
- * through `ListingLayout`'s `mapCenter`/`mapZoom` straight into
- * `ListingMap`'s own `center`/`zoom` props. Omit them to get `ListingMap`'s
- * turnkey auto-fit default instead (see that component's doc comment);
- * supplying `center` opts out of auto-fit entirely.
- */
-type ListingAppMapProp = {
-    provider: MapProvider;
-    center?: LatLng;
-    zoom?: number;
-} | {
-    apiKey: string;
-    mapId?: string;
-    center?: LatLng;
-    zoom?: number;
-};
-interface ListingAppProps<TFilters> {
-    /**
-     * One or more marker-layer datasets; the FIRST entry is the primary
-     * dataset (drives the results list + pagination) -- same "insertion order"
-     * rule `composeListingProviders`/`withDataset` already follow. Entity-erased
-     * (`any`, not `TEntity`) for the same reason `DatasetRegistry<unknown,
-     * TFilters>` is: one array can legitimately hold heterogeneous layers (a
-     * properties dataset and a businesses dataset have different entity types)
-     * -- see `compose-listing-providers.ts`'s `withDataset` doc comment.
-     */
-    datasets: DatasetDefinition<any, TFilters>[];
-    /** A `(reg) => { reg.add(...); }` callback that registers your filters -- forwarded verbatim to `withFilters`. */
-    filters?: (reg: FilterRegistry<TFilters>) => void;
-    /** A ready `MapProvider`, or `{ apiKey, mapId? }` to build a `googleProvider` internally. Omit for no map (the styled layout shows a "Map unavailable" fallback). */
-    map?: ListingAppMapProp;
-    /** Slot overrides, merged OVER the shadcn styled defaults -- see this file's doc comment for how the merge works. */
-    components?: Partial<IListingComponents>;
-    /** A `UrlSyncController<TFilters>`, or `true`. `true` is a documented no-op: the library is filters-shape-erased and cannot generically derive a `TFilters <-> QueryParams` mapping, so build a real controller for your own filter shape. */
-    urlSync?: UrlSyncController<TFilters> | boolean;
-    initialFilters?: TFilters;
-    config?: Partial<IListingConfigOptions>;
-    className?: string;
-    search?: IListingLayoutProps['search'];
-    autoFetch?: boolean;
-}
-/**
- * Turnkey, batteries-included entry point: pass datasets + filters + a map +
- * component overrides + URL sync, and `ListingApp` composes
- * `composeListingProviders(...)`, `<ListingProvider>`, the styled `/shadcn`
- * defaults, and `<ListingLayout>` for you. Equivalent to (and internally
- * built from) the lower-level primitives every other `/shadcn` example wires
- * by hand -- reach for those directly when you need something `ListingApp`
- * doesn't expose (e.g. multiple `<ListingLayout>`s sharing one engine).
- *
- * `TEntity` still can't be inferred from these props (`datasets` narrows it,
- * but a multi-dataset array widens back to the union/`unknown` in practice)
- * -- annotate the call site when entity-level typing matters, exactly like
- * `<ListingProvider<TEntity, TFilters>>` itself.
- *
- * COMPONENTS MERGE: `components` overrides are applied ON TOP of the shadcn
- * styled defaults via ONE explicit `{ ...shadcnDefaultComponents, ...components }`
- * object, passed to a single `<ListingComponentsProvider>` -- never as a
- * nested `<ListingComponentsProvider>` inside `<ListingComponentsProviderWithDefaults>`.
- * `ListingComponentsProvider` merges `provided ?? ITS OWN private, unstyled
- * fallbacks` per slot (it does not read the parent context -- see
- * `src/react/components-provider.tsx`), so nesting would silently discard
- * every un-overridden shadcn default instead of keeping it.
- */
-declare function ListingApp<TEntity, TFilters>(props: ListingAppProps<TFilters>): react.JSX.Element | null;
-
-/** Merges class-name fragments, letting `tailwind-merge` resolve conflicting Tailwind utilities (last one wins). Mirrors `react-wizard-engine`'s `~/utils/cn`. */
-declare function cn(...inputs: ClassValue[]): string;
-
-export { DefaultCard, DefaultEmpty, DefaultFilterPanel, DefaultLoading, DefaultMarker, DefaultPopup, DefaultResultHeader, DefaultSearch, DefaultSidebar, DefaultToolbar, type IListingLayoutProps, ListingApp, type ListingAppMapProp, type ListingAppProps, ListingComponentsProviderWithDefaults, ListingLayout, cn, shadcnDefaultComponents };

package/dist/shadcn/index.d.ts

@@ -1,259 +0,0 @@
-import * as react from 'react';
-import { ReactNode } from 'react';
-import { d as IListingCardProps, e as IListingComponents, f as IListingEmptyProps, g as IListingFilterPanelProps, h as IListingLoadingProps, i as IListingMarkerProps, j as IListingPopupProps, k as IListingResultHeaderProps, l as IListingSearchProps, m as IListingSidebarProps, a as IListingToolbarProps, D as DatasetDefinition, F as FilterRegistry, I as IListingConfigOptions } from '../components-provider-cWVWEDXC.js';
-import { L as LatLng, a as MapProvider } from '../map-provider.interface-DT-v1plm.js';
-import { U as UrlSyncController } from '../url-sync.controller-DK5W_0OZ.js';
-import { ClassValue } from 'clsx';
-
-/**
- * Convenience wrapper around `ListingComponentsProvider` that wires in every
- * package-shipped `Default*` component (via `shadcnDefaultComponents`, the
- * shared source of truth also used by `ListingApp`'s merge). Use this if you
- * want the styled adapter out of the box; use `ListingComponentsProvider`
- * directly (with your own components for some or all slots) otherwise -- the
- * two compose fine since `ListingComponentsProvider` falls back per-slot.
- * Mirrors `react-wizard-engine`'s `WizardComponentsProviderWithDefaults`.
- */
-declare function ListingComponentsProviderWithDefaults({ children }: {
-    children: ReactNode;
-}): react.JSX.Element;
-
-/**
- * Default styled `Card` slot. Renders an optional image, title, subtitle,
- * price and badge from a plain view-model item, and doubles as the
- * clickable/selectable surface (`onSelect`) -- when `onSelect` is provided
- * the card is a `button` rather than a `div` + click handler so it is
- * keyboard operable and announces as a toggle (`aria-pressed`) for free.
- * When `onSelect` is absent (display-only usage) it renders as a
- * non-interactive `<article>` with the same visual classes, minus the
- * button/focus/aria-pressed semantics -- so a purely presentational card
- * doesn't add a no-op tab stop.
- */
-declare function DefaultCard({ item, selected, onSelect }: IListingCardProps): react.JSX.Element;
-
-/**
- * Every `/shadcn` styled default, keyed by slot -- the single source of truth
- * both `ListingComponentsProviderWithDefaults` (spreads it verbatim) and
- * `ListingApp` (spreads a `components` override OVER it) build on.
- *
- * Kept as a plain object, not JSX, so a caller can merge it with
- * `{ ...shadcnDefaultComponents, ...overrides }` and hand the result to ONE
- * `ListingComponentsProvider`. This matters because `ListingComponentsProvider`
- * merges `provided ?? ITS OWN private, UNSTYLED fallbacks` per slot -- it does
- * not read the parent context (see `src/react/components-provider.tsx`).
- * Nesting a `ListingComponentsProvider` (with only the overrides) INSIDE a
- * `ListingComponentsProviderWithDefaults` would therefore silently reset
- * every un-overridden slot back to the bare fallback instead of the shadcn
- * default -- exactly the bug this object exists to avoid.
- */
-declare const shadcnDefaultComponents: IListingComponents;
-
-/** Default styled `Empty` slot: a centered empty state with an icon, heading and hint. */
-declare function DefaultEmpty(_props: IListingEmptyProps): react.JSX.Element;
-
-/** Default styled `FilterPanel` slot: stacks one filter control per row inside `Sidebar`. */
-declare function DefaultFilterPanel({ children }: IListingFilterPanelProps): react.JSX.Element;
-
-/** Default styled `Loading` slot: a shimmering skeleton list, announced via `role="status"`. */
-declare function DefaultLoading(_props: IListingLoadingProps): react.JSX.Element;
-
-/** Default styled `Marker` slot: a small price pill for a map point. */
-declare function DefaultMarker({ point }: IListingMarkerProps): react.JSX.Element;
-
-/**
- * Default styled `Popup` slot: a small card with an accessible close button.
- * `role="group"` + `aria-label` (rather than `role="dialog"`) since this is a
- * non-modal, non-focus-trapped popup anchored to a map marker -- `dialog`
- * without modality/focus management would misrepresent it to AT users.
- */
-declare function DefaultPopup({ entity, onClose }: IListingPopupProps): react.JSX.Element;
-
-/** Default styled `ResultHeader` slot: `"{count} results"`, or `"{count} of {total} results"` when a distinct total is known. */
-declare function DefaultResultHeader({ count, total }: IListingResultHeaderProps): react.JSX.Element;
-
-/** Default styled `Search` slot: a plain styled text input. */
-declare function DefaultSearch({ value, onChange, placeholder }: IListingSearchProps): react.JSX.Element;
-
-/**
- * Default styled `Sidebar` slot: the outer chrome for the filters column in
- * `ListingLayout`. Full width and unbordered on mobile (stacks above the
- * results in normal document flow); becomes a fixed-width bordered rail from
- * `md` up.
- */
-declare function DefaultSidebar({ children }: IListingSidebarProps): react.JSX.Element;
-
-/** Default styled `Toolbar` slot: a bordered bar wrapping arbitrary children. */
-declare function DefaultToolbar({ children }: IListingToolbarProps): react.JSX.Element;
-
-interface IListingLayoutProps {
-    /**
-     * Optional search box, wired by the CONSUMER into their own `TFilters`
-     * shape. `ListingLayout` is filters-shape-erased (same reasoning as the
-     * engine itself -- see `ListingEngineOptions`'s docstring) so it cannot
-     * derive a generic "search" filter on its own; when omitted, no search box
-     * is rendered at all. Documented, deliberate scope: wiring a named
-     * "search" filter convention end-to-end is a future enhancement.
-     */
-    search?: {
-        value: string;
-        onChange: (value: string) => void;
-        placeholder?: string;
-    };
-    className?: string;
-    /** Extra content rendered at the end of the filter bar, alongside `ListingResultHeader` (e.g. a sort control). */
-    toolbarEnd?: ReactNode;
-    /**
-     * Whether `ListingLayout` fetches the first page itself on mount
-     * (`engine.applyFilters({})`). Defaults to `true` (batteries-included).
-     * Pass `false` to defer the initial fetch to the caller -- e.g. a
-     * search-before-results flow, or when `urlSync` hydrates filters from the
-     * URL and should drive the first fetch instead of racing it.
-     */
-    autoFetch?: boolean;
-    /**
-     * Forwarded verbatim to `<ListingMap center={mapCenter} />`. Omit to get
-     * `ListingMap`'s turnkey auto-fit default (frames the map to its own data
-     * once it loads) -- passing `mapCenter` opts OUT of auto-fit entirely, on
-     * the theory that an explicit initial view is a deliberate choice
-     * (see `ListingMap`'s doc comment's "Auto-fit" section).
-     */
-    mapCenter?: LatLng;
-    /** Forwarded verbatim to `<ListingMap zoom={mapZoom} />`. See `mapCenter`. */
-    mapZoom?: number;
-}
-/**
- * Full, responsive default listing experience, matching the "top filter bar
- * + list-left/map-right split" pattern of a typical `/find` real-estate
- * search page: a sticky horizontal filter bar (search + filter groups +
- * result count), then below it a split -- a scrollable card grid on the left
- * and a full-height map on the right. Composed entirely from the
- * structure-only compound components in `~/react` plus the injected slot
- * components (via `useListingComponents()` for `Search`, and implicitly
- * through each compound component for `Card`/`Empty`/`Loading`/etc.) -- this
- * file adds layout/chrome only, no new business logic.
- *
- * Layout choices (documented, not the only valid ones):
- * - FILTER BAR (`data-slot="listing-layout-filter-bar"`): `sticky top-0`,
- *   `border-b`/`bg-background`, and a `flex flex-wrap items-end gap-3` row
- *   containing the injected `Search` (when `search` is passed),
- *   `<ListingFilters>` (given the same horizontal row className plus a
- *   `min-w-0` `groupClassName` so individual groups can shrink instead of
- *   forcing overflow), and a trailing `ml-auto` cluster with
- *   `<ListingResultHeader>` + `toolbarEnd`. `flex-wrap` is what makes this
- *   gracefully reflow on narrow widths -- groups drop to new lines instead
- *   of overflowing or requiring a separate mobile-only layout.
- * - SPLIT (`data-slot="listing-layout-split"`): a single CSS grid,
- *   `md:grid-cols-[minmax(340px,42%)_1fr]` from `md` up (list column floors
- *   at 340px, caps at 42% of the split's width; map takes the rest). Below
- *   `md` there is no grid -- just two full-width panels, and exactly one is
- *   visible at a time (see the mobile toggle below).
- * - LIST region (`data-slot="listing-layout-list"`): `overflow-y-auto`, its
- *   own scroll container so browsing the list never requires scrolling the
- *   map out of view. Holds `<ListingList>` (an auto-fill card grid) and
- *   `<ListingPagination>`.
- * - MAP region (`data-slot="listing-layout-map"`): fills the split's full
- *   height via the grid's default stretch alignment (no explicit height
- *   needed), plus `md:sticky md:top-0` so that if a consuming app ever lets
- *   `ListingLayout` sit inside a naturally document-scrolling page (rather
- *   than the fixed-height shell this component defaults to via
- *   `h-full min-h-0`), the map still pins in place while the list scrolls
- *   past -- inert (but harmless) in the default fixed-height composition,
- *   where there is nothing above the split to scroll past in the first
- *   place. Renders `<ListingMap>` with a default centered fallback message
- *   (`MAP_FALLBACK`) for when no `MapProvider` is configured, so the pane
- *   never looks broken/blank.
- * - MOBILE LIST/MAP TOGGLE (`data-slot="listing-layout-mobile-toggle"`,
- *   `md:hidden`): a small two-button segmented control, local `useState`
- *   (`mobileView`), defaulting to `'list'`. Both the list and map regions
- *   stay mounted at all times (never remounted on toggle -- that would
- *   re-trigger `ListingList`'s/`ListingMap`'s own mount effects for no
- *   reason); only their visibility flips via `hidden md:block` /
- *   `block md:block`, i.e. the toggle only ever matters below `md` -- at
- *   `md` and up both regions are always visible side by side and the toggle
- *   control itself is hidden.
- * - Fetches the first page itself on mount (`engine.applyFilters({})`) by
- *   default: none of the structure-only `~/react` compound components do
- *   this (they are deliberately side-effect-free), so as the
- *   batteries-included "full experience" entry point, `ListingLayout` is the
- *   natural, single owner of that one bootstrapping side effect. Pass
- *   `autoFetch={false}` to opt out and drive the first fetch yourself (e.g.
- *   search-before-results, or when `urlSync` hydrates filters from the URL).
- */
-declare function ListingLayout({ search, className, toolbarEnd, autoFetch, mapCenter, mapZoom, }: IListingLayoutProps): react.JSX.Element;
-
-/**
- * `ListingApp.map` accepts either a ready-made `MapProvider` (any
- * implementation -- Google, a fake, a future provider) or, as a convenience,
- * a bare Google Maps API key. See `useResolvedMap`'s doc comment for why the
- * key shorthand is resolved via a dynamic `import()` rather than a static one.
- *
- * Both shapes optionally carry `center`/`zoom` -- the initial view, forwarded
- * through `ListingLayout`'s `mapCenter`/`mapZoom` straight into
- * `ListingMap`'s own `center`/`zoom` props. Omit them to get `ListingMap`'s
- * turnkey auto-fit default instead (see that component's doc comment);
- * supplying `center` opts out of auto-fit entirely.
- */
-type ListingAppMapProp = {
-    provider: MapProvider;
-    center?: LatLng;
-    zoom?: number;
-} | {
-    apiKey: string;
-    mapId?: string;
-    center?: LatLng;
-    zoom?: number;
-};
-interface ListingAppProps<TFilters> {
-    /**
-     * One or more marker-layer datasets; the FIRST entry is the primary
-     * dataset (drives the results list + pagination) -- same "insertion order"
-     * rule `composeListingProviders`/`withDataset` already follow. Entity-erased
-     * (`any`, not `TEntity`) for the same reason `DatasetRegistry<unknown,
-     * TFilters>` is: one array can legitimately hold heterogeneous layers (a
-     * properties dataset and a businesses dataset have different entity types)
-     * -- see `compose-listing-providers.ts`'s `withDataset` doc comment.
-     */
-    datasets: DatasetDefinition<any, TFilters>[];
-    /** A `(reg) => { reg.add(...); }` callback that registers your filters -- forwarded verbatim to `withFilters`. */
-    filters?: (reg: FilterRegistry<TFilters>) => void;
-    /** A ready `MapProvider`, or `{ apiKey, mapId? }` to build a `googleProvider` internally. Omit for no map (the styled layout shows a "Map unavailable" fallback). */
-    map?: ListingAppMapProp;
-    /** Slot overrides, merged OVER the shadcn styled defaults -- see this file's doc comment for how the merge works. */
-    components?: Partial<IListingComponents>;
-    /** A `UrlSyncController<TFilters>`, or `true`. `true` is a documented no-op: the library is filters-shape-erased and cannot generically derive a `TFilters <-> QueryParams` mapping, so build a real controller for your own filter shape. */
-    urlSync?: UrlSyncController<TFilters> | boolean;
-    initialFilters?: TFilters;
-    config?: Partial<IListingConfigOptions>;
-    className?: string;
-    search?: IListingLayoutProps['search'];
-    autoFetch?: boolean;
-}
-/**
- * Turnkey, batteries-included entry point: pass datasets + filters + a map +
- * component overrides + URL sync, and `ListingApp` composes
- * `composeListingProviders(...)`, `<ListingProvider>`, the styled `/shadcn`
- * defaults, and `<ListingLayout>` for you. Equivalent to (and internally
- * built from) the lower-level primitives every other `/shadcn` example wires
- * by hand -- reach for those directly when you need something `ListingApp`
- * doesn't expose (e.g. multiple `<ListingLayout>`s sharing one engine).
- *
- * `TEntity` still can't be inferred from these props (`datasets` narrows it,
- * but a multi-dataset array widens back to the union/`unknown` in practice)
- * -- annotate the call site when entity-level typing matters, exactly like
- * `<ListingProvider<TEntity, TFilters>>` itself.
- *
- * COMPONENTS MERGE: `components` overrides are applied ON TOP of the shadcn
- * styled defaults via ONE explicit `{ ...shadcnDefaultComponents, ...components }`
- * object, passed to a single `<ListingComponentsProvider>` -- never as a
- * nested `<ListingComponentsProvider>` inside `<ListingComponentsProviderWithDefaults>`.
- * `ListingComponentsProvider` merges `provided ?? ITS OWN private, unstyled
- * fallbacks` per slot (it does not read the parent context -- see
- * `src/react/components-provider.tsx`), so nesting would silently discard
- * every un-overridden shadcn default instead of keeping it.
- */
-declare function ListingApp<TEntity, TFilters>(props: ListingAppProps<TFilters>): react.JSX.Element | null;
-
-/** Merges class-name fragments, letting `tailwind-merge` resolve conflicting Tailwind utilities (last one wins). Mirrors `react-wizard-engine`'s `~/utils/cn`. */
-declare function cn(...inputs: ClassValue[]): string;
-
-export { DefaultCard, DefaultEmpty, DefaultFilterPanel, DefaultLoading, DefaultMarker, DefaultPopup, DefaultResultHeader, DefaultSearch, DefaultSidebar, DefaultToolbar, type IListingLayoutProps, ListingApp, type ListingAppMapProp, type ListingAppProps, ListingComponentsProviderWithDefaults, ListingLayout, cn, shadcnDefaultComponents };

package/dist/shadcn/index.js

@@ -1,2 +0,0 @@
-"use client";
-import{a as K}from"../chunk-35KYEBAC.js";import{A as X,B as Y,h as U,i as H,j as _,k as O,l as W,m as z,n as B,p as v,q as $,s as Z,v as G,x as q,y as J,z as Q}from"../chunk-R3FX2V3N.js";import{clsx as ie}from"clsx";import{twMerge as se}from"tailwind-merge";function s(...e){return se(ie(e))}import{Fragment as ne,jsx as m,jsxs as N}from"react/jsx-runtime";function ae(e){return typeof e!="number"?e:new Intl.NumberFormat("en-US",{style:"currency",currency:"USD",maximumFractionDigits:0}).format(e)}function w({item:e,selected:o,onSelect:t}){let r=e??{},l=s("flex w-full flex-col overflow-hidden rounded-lg border bg-card text-left text-card-foreground shadow-sm","motion-safe:transition-shadow",t&&"hover:shadow-md focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring",o&&"ring-2 ring-ring"),a=N(ne,{children:[r.imageUrl&&m("img",{src:r.imageUrl,alt:r.title??"",className:"aspect-video w-full rounded-t-lg object-cover"}),N("div",{className:"flex flex-1 flex-col gap-1 p-3",children:[N("div",{className:"flex items-start justify-between gap-2",children:[r.title&&m("span",{className:"font-medium",children:r.title}),r.badge&&m("span",{className:"shrink-0 rounded-full bg-muted px-2 py-0.5 text-xs font-medium text-muted-foreground",children:r.badge})]}),r.subtitle&&m("span",{className:"text-sm text-muted-foreground",children:r.subtitle}),r.price!=null&&m("span",{className:"mt-1 font-semibold tabular-nums",children:ae(r.price)})]})]});return t?m("button",{type:"button",onClick:t,"aria-pressed":o??!1,className:l,children:a}):m("article",{className:l,children:a})}import{jsx as x,jsxs as j}from"react/jsx-runtime";function C(e){return j("div",{role:"status",className:"flex flex-col items-center justify-center gap-2 px-4 py-12 text-center text-muted-foreground",children:[j("svg",{xmlns:"http://www.w3.org/2000/svg",viewBox:"0 0 24 24",fill:"none",stroke:"currentColor",strokeWidth:1.5,strokeLinecap:"round",strokeLinejoin:"round",className:"h-8 w-8","aria-hidden":"true",children:[x("circle",{cx:"11",cy:"11",r:"7"}),x("path",{d:"m21 21-4.3-4.3"})]}),x("p",{className:"text-sm font-medium text-foreground",children:"No results"}),x("p",{className:"text-xs text-muted-foreground",children:"Try adjusting your filters or search terms."})]})}import{jsx as le}from"react/jsx-runtime";function I({children:e}){return le("div",{className:"flex flex-col gap-3",children:e})}import{jsx as L,jsxs as pe}from"react/jsx-runtime";function D(e){return L("div",{className:"flex flex-col gap-3 p-3",role:"status","aria-busy":"true","aria-label":"Loading results",children:Array.from({length:3}).map((o,t)=>pe("div",{className:"flex flex-col gap-2 motion-safe:animate-pulse",children:[L("div",{className:"aspect-video w-full rounded-md bg-muted"}),L("div",{className:"h-4 w-2/3 rounded-md bg-muted"}),L("div",{className:"h-3 w-1/3 rounded-md bg-muted"})]},t))})}import{jsx as de}from"react/jsx-runtime";function M({point:e}){let o=e.entity??{};return de("span",{className:"rounded-full border bg-background px-2 py-0.5 text-xs font-medium tabular-nums shadow-sm",children:o.price??""})}import{jsx as c,jsxs as k}from"react/jsx-runtime";function F({entity:e,onClose:o}){let t=e??{};return k("div",{className:"relative w-64 rounded-lg border bg-popover p-3 text-popover-foreground shadow-md",role:"group","aria-label":"Location details",children:[c("button",{type:"button",onClick:o,"aria-label":"Close",className:"absolute right-2 top-2 rounded-md p-1 text-muted-foreground motion-safe:transition-colors hover:bg-foreground/[0.06] hover:text-foreground focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring",children:k("svg",{xmlns:"http://www.w3.org/2000/svg",viewBox:"0 0 24 24",fill:"none",stroke:"currentColor",strokeWidth:2,strokeLinecap:"round",strokeLinejoin:"round",className:"h-4 w-4","aria-hidden":"true",children:[c("path",{d:"M18 6 6 18"}),c("path",{d:"m6 6 12 12"})]})}),k("div",{className:"pr-6",children:[t.title&&c("div",{className:"font-medium",children:t.title}),t.subtitle&&c("div",{className:"text-sm text-muted-foreground",children:t.subtitle}),t.price!=null&&c("div",{className:"mt-1 font-semibold tabular-nums",children:t.price})]})]})}import{jsx as me}from"react/jsx-runtime";function S({count:e,total:o}){let t=o!=null&&o!==e?`${e} of ${o} results`:`${e} results`;return me("div",{className:"text-sm tabular-nums text-muted-foreground",children:t})}import{jsx as ue}from"react/jsx-runtime";function T({value:e,onChange:o,placeholder:t}){return ue("input",{type:"search",value:e,placeholder:t,onChange:r=>o(r.target.value),"aria-label":t??"Search",className:s("h-9 w-full rounded-md border bg-background px-3 text-sm text-foreground placeholder:text-muted-foreground","focus-visible:border-ring focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring")})}import{jsx as fe}from"react/jsx-runtime";function R({children:e}){return fe("aside",{className:"flex w-full flex-col gap-4 p-4 md:border-r md:border-border",children:e})}import{jsx as ce}from"react/jsx-runtime";function A({children:e}){return ce("div",{className:"flex items-center gap-2 border-b p-2",children:e})}var g={Card:w,Marker:M,Popup:F,Sidebar:R,FilterPanel:I,Search:T,Empty:C,Loading:D,ResultHeader:S,Toolbar:A};import{jsx as be}from"react/jsx-runtime";function ge({children:e}){return be(v,{...g,children:e})}import{useEffect as ye,useState as he}from"react";import{useEffect as ve,useState as xe}from"react";import{jsx as i,jsxs as b}from"react/jsx-runtime";var Le=i("p",{className:"px-4 text-center text-sm text-muted-foreground",children:"Map unavailable - provide a Google Maps API key"});function E({search:e,className:o,toolbarEnd:t,autoFetch:r=!0,mapCenter:l,mapZoom:a}){let p=Z(),{Search:u}=$(),[f,y]=xe("list");ve(()=>{r!==!1&&p.applyFilters({})},[p,r]);let h=f==="map"?"hidden md:block":"block",P=f==="list"?"hidden md:block":"block";return b("div",{className:s("flex h-full min-h-0 w-full flex-col bg-background text-foreground",o),"data-slot":"listing-layout",children:[b("div",{className:"sticky top-0 z-10 flex flex-wrap items-end gap-3 border-b border-border bg-background p-3","data-slot":"listing-layout-filter-bar",children:[e&&i("div",{className:"w-full min-w-0 sm:w-auto sm:max-w-xs sm:flex-1",children:i(u,{value:e.value,onChange:e.onChange,placeholder:e.placeholder})}),i(G,{className:"flex flex-wrap items-end gap-3",groupClassName:"min-w-0"}),b("div",{className:"ml-auto flex items-center gap-3",children:[i(X,{}),t]})]}),i("div",{className:"flex items-center justify-center gap-1 border-b border-border bg-background p-2 md:hidden","data-slot":"listing-layout-mobile-toggle",children:i("div",{role:"group","aria-label":"View",className:"inline-flex rounded-md border border-border p-0.5",children:[{view:"list",label:"List"},{view:"map",label:"Map"}].map(({view:d,label:n})=>i("button",{type:"button","aria-pressed":f===d,onClick:()=>y(d),className:s("rounded-[5px] px-3 py-1 text-sm font-medium motion-safe:transition-colors",f===d?"bg-primary text-primary-foreground":"text-muted-foreground hover:bg-foreground/[0.06] hover:text-foreground"),children:n},d))})}),b("div",{className:"grid min-h-0 flex-1 md:grid-cols-[minmax(340px,42%)_1fr]","data-slot":"listing-layout-split",children:[b("div",{className:s("min-h-0 overflow-y-auto p-3",h),"data-slot":"listing-layout-list",children:[i(q,{className:"grid content-start gap-3 [grid-template-columns:repeat(auto-fill,minmax(200px,1fr))]"}),i("div",{className:"mt-4 flex justify-center",children:i(Q,{})})]}),i("div",{className:s("min-h-0 md:sticky md:top-0",P),"data-slot":"listing-layout-map",children:i(J,{center:l,zoom:a,fallback:Le})})]})]})}import{jsx as V}from"react/jsx-runtime";function ee(e){return"provider"in e}function Pe(e){let o=e!=null&&!ee(e),t=o?e.apiKey:void 0,r=o?e.mapId:void 0,[l,a]=he(()=>!e||ee(e)?{ready:!0,provider:e?.provider}:{ready:!1});return ye(()=>{if(!t)return;let p=!1;return import("../maps/google/index.js").then(({googleProvider:u})=>{p||a({ready:!0,provider:u({apiKey:t,mapId:r})})}),()=>{p=!0}},[t,r]),l}function Ne(e){let{datasets:o,filters:t,map:r,components:l,urlSync:a,initialFilters:p,config:u,className:f,search:y,autoFetch:h}=e,{ready:P,provider:d}=Pe(r);if(!P)return null;let n=[];for(let oe of o)n.push(O(oe));t&&n.push(W(t)),d&&n.push(_(d)),a instanceof K&&n.push(z(a)),p&&n.push(B(p)),u&&n.push(H(u));let te=U(...n),re={...g,...l};return V(Y,{...te,children:V(v,{...re,children:V(E,{className:f,search:y,autoFetch:h,mapCenter:r?.center,mapZoom:r?.zoom})})})}export{w as DefaultCard,C as DefaultEmpty,I as DefaultFilterPanel,D as DefaultLoading,M as DefaultMarker,F as DefaultPopup,S as DefaultResultHeader,T as DefaultSearch,R as DefaultSidebar,A as DefaultToolbar,Ne as ListingApp,ge as ListingComponentsProviderWithDefaults,E as ListingLayout,s as cn,g as shadcnDefaultComponents};

package/dist/url-sync.controller-DK5W_0OZ.d.ts

@@ -1,89 +0,0 @@
-import { Q as QueryParams } from './map-provider.interface-DT-v1plm.js';
-
-/**
- * DOM-agnostic abstraction over "the URL's query string" — or, in tests/SSR,
- * an in-memory stand-in (`MemoryHistoryPort`). `UrlSyncController` talks to
- * this interface only, never to `window.location`/`history` directly, so it
- * stays framework- and environment-free like the rest of `src/core`.
- */
-interface HistoryPort {
-    getQuery(): QueryParams;
-    setQuery(params: QueryParams): void;
-    subscribe(cb: () => void): () => void;
-}
-
-interface UrlSyncEngine<TFilters> {
-    subscribe(cb: () => void): () => void;
-    readonly state: {
-        readonly filters: TFilters;
-    };
-    applyFilters(patch: Partial<TFilters>): Promise<void> | void;
-}
-interface UrlSyncOptions<TFilters> {
-    history: HistoryPort;
-    toQuery(filters: TFilters): QueryParams;
-    toFilters(query: QueryParams): Partial<TFilters>;
-    hydrateOnStart?: boolean;
-}
-/**
- * Bidirectional, DOM-agnostic sync between an engine's `filters` and a
- * `HistoryPort`'s query params. Framework-free: talks to `UrlSyncEngine`
- * (a structural subset `ListingEngine` satisfies) and `HistoryPort`, nothing
- * else — no `window`, no React.
- *
- * OPTIONAL, not the primary path: `styled/listing-app.tsx`'s turnkey
- * `ListingApp` (the package's main-entry default) does NOT wire this up —
- * it uses an event-based URL API instead (`initialFilters` in,
- * `onFiltersChange` out; see that file's doc comment), so the library never
- * touches `window.history` by default. This class remains exported for
- * consumers who explicitly want the library to own history writes/reads
- * itself (e.g. via `/shadcn`'s `ListingApp.urlSync`, or wiring it directly
- * against a hand-built engine).
- *
- * Echo-loop guard: both subscriptions below are driven by the SAME
- * `isSyncing` flag. `ListingEngine.applyFilters()` and `MemoryHistoryPort`
- * (and any real browser HistoryPort) both notify their subscribers
- * SYNCHRONOUSLY as part of the write (`store.setFilters()` -> `notify()`
- * happens before any debounce timer, and `MemoryHistoryPort.setQuery()`
- * notifies before returning) — so when this controller initiates a write on
- * one side, the reciprocal subscription on the other side fires within the
- * very same call stack, before `isSyncing` is reset. Wrapping each
- * controller-initiated write in `isSyncing = true; ...; isSyncing = false`
- * (via try/finally, so a throwing `toQuery`/`toFilters`/notify can't leave it
- * stuck) means that reciprocal callback observes `isSyncing === true` and
- * short-circuits instead of writing back — one hop each direction, never a
- * cascade. `hydrateOnStart`'s initial engine write is wrapped the same way,
- * since it must not immediately echo the just-hydrated filters back out to
- * history as a redundant `setQuery`.
- *
- * `isSyncing` only covers that SYNCHRONOUS window, though — the real
- * `ListingEngine.applyFilters()` notifies AGAIN, asynchronously: after
- * `await adapter.list(...)` resolves, `store.setResults()` and
- * `store.setLoading(false)` each call `notify()`, well after `isSyncing` has
- * already been reset to `false` by the `withSyncGuard` that kicked the query
- * off. Left unguarded, that async tail would fire the engine subscription
- * below and echo an identical (but spurious) `history.setQuery(...)` on
- * every completed query. Rather than widening `isSyncing` to cover the whole
- * async query (which would also swallow legitimate concurrent history
- * changes that land mid-query), `syncEngineToHistory` is idempotent BY
- * VALUE instead: it computes the target query and skips the write entirely
- * when it already matches `history.getQuery()` — timing-independent, so it
- * suppresses the async-tail echo without touching `isSyncing` at all.
- */
-declare class UrlSyncController<TFilters> {
-    private readonly history;
-    private readonly toQueryFn;
-    private readonly toFiltersFn;
-    private readonly hydrateOnStart;
-    private isSyncing;
-    private unsubscribeEngine;
-    private unsubscribeHistory;
-    constructor(opts: UrlSyncOptions<TFilters>);
-    start(engine: UrlSyncEngine<TFilters>): void;
-    stop(): void;
-    private syncEngineToHistory;
-    private applyFiltersSafely;
-    private withSyncGuard;
-}
-
-export { type HistoryPort as H, UrlSyncController as U, type UrlSyncEngine as a, type UrlSyncOptions as b };