@stapel/search-react 0.4.0 → 0.7.0

package/src/i18n/keys.ts

@@ -54,6 +54,16 @@ export const SEARCH_I18N_KEYS = {
   resultsDistanceKm: "search.results.distance_km",
   resultsUntitled: "search.results.untitled",
   resultsOpen: "search.results.open",
+  /** Alt text for the card photo — the card's own title, in a sentence. */
+  resultsImageAlt: "search.results.image_alt",
+
+  // ── the query box ────────────────────────────────────────────────────────
+  boxLabel: "search.box.label",
+  boxPlaceholder: "search.box.placeholder",
+  boxSubmit: "search.box.submit",
+  boxClear: "search.box.clear",
+  /** Accessible name of the suggestion list under the box. */
+  boxSuggestions: "search.box.suggestions",
 
   // ── sort ─────────────────────────────────────────────────────────────────
   sortLabel: "search.sort.label",
@@ -79,10 +89,45 @@ export const SEARCH_I18N_KEYS = {
   facetsRangeFrom: "search.facets.range_from",
   facetsRangeTo: "search.facets.range_to",
   facetsRangeApply: "search.facets.range_apply",
+  facetsRangeClear: "search.facets.range_clear",
+  /** Accessible names: the visible "From"/"To" repeat on every row, so the
+   * field's own name has to carry the feature it belongs to. */
+  facetsRangeFromAria: "search.facets.range_from_aria",
+  facetsRangeToAria: "search.facets.range_to_aria",
+  /** The reason "Apply" is off: the range reads backwards. */
+  facetsRangeInvalid: "search.facets.range_invalid",
+
+  // ── the filter panel as a whole (phone sheet + host slots) ───────────────
+  filtersOpen: "search.filters.open",
+  /** The sheet's commit button when the count is unknown. */
+  filtersApply: "search.filters.apply",
+  /** "Show N results" — an EXACT count on the sheet's commit button.
+   * A PLURAL FAMILY. */
+  filtersShowCount: "search.filters.show_count",
+  /** "Show N+ results" — a FLOOR on the same button. A PLURAL FAMILY. */
+  filtersShowCountAtLeast: "search.filters.show_count_at_least",
+  filtersDismiss: "search.filters.dismiss",
+
+  // ── category (a host slot, plus the control that removes it) ─────────────
+  categoryTitle: "search.category.title",
+  categoryClear: "search.category.clear",
+  categoryCurrent: "search.category.current",
+
+  // ── language of the query ────────────────────────────────────────────────
+  languageLabel: "search.language.label",
+  languageAny: "search.language.any",
+
+  // ── page size ────────────────────────────────────────────────────────────
+  limitLabel: "search.limit.label",
+  limitOption: "search.limit.option",
+  /** Said beside the control when the URL carries a size the ladder does not
+   * offer — otherwise the story of "we kept your link's size" is invisible. */
+  limitFromLink: "search.limit.from_link",
 
   // ── geo ──────────────────────────────────────────────────────────────────
   geoTitle: "search.geo.title",
   geoRadiusKm: "search.geo.radius_km",
+  geoRadiusLabel: "search.geo.radius_label",
   geoClear: "search.geo.clear",
   geoBox: "search.geo.box",
   geoCenter: "search.geo.center",
@@ -140,6 +185,8 @@ export const SEARCH_I18N_PLURAL_KEYS: readonly SearchI18nKey[] = [
   SEARCH_I18N_KEYS.resultsCountApproximate,
   SEARCH_I18N_KEYS.resultsCountAtLeast,
   SEARCH_I18N_KEYS.resultsCountExact,
+  SEARCH_I18N_KEYS.filtersShowCount,
+  SEARCH_I18N_KEYS.filtersShowCountAtLeast,
 ];
 
 /**
@@ -176,6 +223,13 @@ export const searchI18nBundleEn: Record<string, string> = {
   "search.results.distance_km": "{km} km away",
   "search.results.untitled": "Untitled",
   "search.results.open": "Open",
+  "search.results.image_alt": "Photo of {title}",
+
+  "search.box.label": "Search",
+  "search.box.placeholder": "What are you looking for?",
+  "search.box.submit": "Search",
+  "search.box.clear": "Clear the search",
+  "search.box.suggestions": "Suggestions",
 
   "search.sort.label": "Sort",
   "search.sort.relevance": "Most relevant",
@@ -201,21 +255,46 @@ export const searchI18nBundleEn: Record<string, string> = {
   "search.facets.range_from": "From",
   "search.facets.range_to": "To",
   "search.facets.range_apply": "Apply",
+  "search.facets.range_clear": "Clear",
+  "search.facets.range_from_aria": "{feature}, from",
+  "search.facets.range_to_aria": "{feature}, up to",
+  "search.facets.range_invalid":
+    "“From” is larger than “to”, so nothing could match. Swap them to apply this range.",
+
+  "search.filters.open": "Filters ({count})",
+  "search.filters.apply": "Show results",
+  "search.filters.show_count.one": "Show {count} result",
+  "search.filters.show_count.other": "Show {count} results",
+  "search.filters.show_count_at_least.one": "Show {count}+ result",
+  "search.filters.show_count_at_least.other": "Show {count}+ results",
+  "search.filters.dismiss": "Close the filters",
+
+  "search.category.title": "Category",
+  "search.category.clear": "Search the whole catalogue",
+  "search.category.current": "Searching inside {path}",
+
+  "search.language.label": "Query language",
+  "search.language.any": "Any language",
+
+  "search.limit.label": "Per page",
+  "search.limit.option": "{count} per page",
+  "search.limit.from_link": "This link sets its own page size.",
 
   "search.geo.title": "Location",
   "search.geo.radius_km": "Within {km} km",
+  "search.geo.radius_label": "Radius, km",
   "search.geo.clear": "Anywhere",
   "search.geo.box": "Inside the shown area",
   "search.geo.center": "Around {lat}, {lon}",
 
   "search.url.issues_title": "Part of this link could not be read",
-  "search.url.issue.not_a_number": "{param} is not a number and was ignored",
+  "search.url.issue.not_a_number": "“{param}” in this link is not a number, so it was ignored",
   "search.url.issue.geo_incomplete":
-    "the location needs both lat and lon, so it was ignored",
+    "the location in this link is only half there, so it was ignored",
   "search.url.issue.bbox_malformed":
-    "the area needs four numbers (minLat,minLon,maxLat,maxLon) and was ignored",
+    "the map area in this link is incomplete, so it was ignored",
   "search.url.issue.range_malformed":
-    "{param} is not a from..to range and was ignored",
+    "the range “{param}” in this link needs two numbers, so it was ignored",
 
   "search.degraded.title": "What this search could not do",
   "search.degraded.typo_tolerance":

package/src/i18n/ru.ts

@@ -62,6 +62,13 @@ export const searchI18nBundleRu: I18nDictionary = {
   "search.results.distance_km": "{km} км от вас",
   "search.results.untitled": "Без названия",
   "search.results.open": "Открыть",
+  "search.results.image_alt": "Фото: {title}",
+
+  "search.box.label": "Поиск",
+  "search.box.placeholder": "Что ищете?",
+  "search.box.submit": "Найти",
+  "search.box.clear": "Очистить запрос",
+  "search.box.suggestions": "Подсказки",
 
   "search.sort.label": "Сортировка",
   "search.sort.relevance": "По релевантности",
@@ -87,21 +94,51 @@ export const searchI18nBundleRu: I18nDictionary = {
   "search.facets.range_from": "От",
   "search.facets.range_to": "До",
   "search.facets.range_apply": "Применить",
+  "search.facets.range_clear": "Сбросить",
+  "search.facets.range_from_aria": "{feature}, от",
+  "search.facets.range_to_aria": "{feature}, до",
+  "search.facets.range_invalid":
+    "«От» больше, чем «до», — под такой диапазон ничего не подойдёт. Поменяйте значения местами.",
+
+  "search.filters.open": "Фильтры ({count})",
+  "search.filters.apply": "Показать результаты",
+  "search.filters.show_count.one": "Показать {count} объявление",
+  "search.filters.show_count.few": "Показать {count} объявления",
+  "search.filters.show_count.many": "Показать {count} объявлений",
+  "search.filters.show_count.other": "Показать {count} объявления",
+  "search.filters.show_count_at_least.one": "Показать {count}+ объявление",
+  "search.filters.show_count_at_least.few": "Показать {count}+ объявления",
+  "search.filters.show_count_at_least.many": "Показать {count}+ объявлений",
+  "search.filters.show_count_at_least.other": "Показать {count}+ объявления",
+  "search.filters.dismiss": "Закрыть фильтры",
+
+  "search.category.title": "Категория",
+  "search.category.clear": "Искать по всему каталогу",
+  "search.category.current": "Ищем внутри {path}",
+
+  "search.language.label": "Язык запроса",
+  "search.language.any": "Любой язык",
+
+  "search.limit.label": "На странице",
+  "search.limit.option": "{count} на странице",
+  "search.limit.from_link": "Размер страницы задан этой ссылкой.",
 
   "search.geo.title": "Где искать",
   "search.geo.radius_km": "В радиусе {km} км",
+  "search.geo.radius_label": "Радиус, км",
   "search.geo.clear": "Везде",
   "search.geo.box": "В показанной области",
   "search.geo.center": "Рядом с {lat}, {lon}",
 
   "search.url.issues_title": "Часть этой ссылки прочитать не удалось",
-  "search.url.issue.not_a_number": "{param} — не число, параметр пропущен",
+  "search.url.issue.not_a_number":
+    "«{param}» в этой ссылке — не число, поэтому параметр пропущен",
   "search.url.issue.geo_incomplete":
-    "для точки нужны и lat, и lon — параметр пропущен",
+    "точка в этой ссылке указана наполовину, поэтому она пропущена",
   "search.url.issue.bbox_malformed":
-    "для области нужны четыре числа (minLat,minLon,maxLat,maxLon) — параметр пропущен",
+    "область на карте в этой ссылке указана не полностью, поэтому она пропущена",
   "search.url.issue.range_malformed":
-    "{param} — не диапазон вида from..to, параметр пропущен",
+    "диапазону «{param}» в этой ссылке не хватает чисел, поэтому он пропущен",
 
   "search.degraded.title": "Что этот поиск не смог сделать",
   "search.degraded.typo_tolerance":

package/src/index.ts

@@ -102,6 +102,24 @@ export type {
   FacetOption,
 } from "./state/facets.js";
 
+export {
+  RANGE_FEATURE_TYPES,
+  buildRangeGroups,
+  isRangeFeature,
+  isRangeUsable,
+} from "./state/ranges.js";
+export type { BuildRangeGroupsInput, RangeGroup } from "./state/ranges.js";
+
+export {
+  SEARCH_BOX_DEBOUNCE_MS,
+  SEARCH_BOX_SUGGEST_DEBOUNCE_MS,
+  SEARCH_DEFAULT_PAGE_SIZE,
+  SEARCH_MAX_PAGE_SIZE,
+  SEARCH_QUERY_MAX_CHARS,
+  SUGGEST_MAX_LIMIT,
+  SUGGEST_MIN_CHARS,
+} from "./state/limits.js";
+
 // ── model (runtime wiring, query keys, context, hooks) ───────────────────────
 export { createSearchRuntime } from "./model/runtime.js";
 export type {
@@ -117,7 +135,7 @@ export {
 export { searchQueryKeys } from "./model/queryKeys.js";
 export type { SearchQueryKeyParams } from "./model/queryKeys.js";
 
-export { useRankingDisclosure, useSearchQuery } from "./model/queries.js";
+export { useRankingDisclosure, useSearchQuery, useSuggest } from "./model/queries.js";
 
 // ── headless (renderless components) ─────────────────────────────────────────
 export { SearchProvider } from "./headless/SearchProvider.js";
@@ -129,9 +147,11 @@ export type {
 } from "./headless/SearchStateProvider.js";
 export { SearchResults } from "./headless/SearchResults.js";
 export type { SearchPageInfo, SearchResultsBag } from "./headless/SearchResults.js";
-export { FacetPanel } from "./headless/FacetPanel.js";
+export { FacetPanel, useFacetPanel } from "./headless/FacetPanel.js";
 export type { FacetPanelBag } from "./headless/FacetPanel.js";
 export { useAppliedSort } from "./headless/useAppliedSort.js";
+export { useSearchBox } from "./headless/useSearchBox.js";
+export type { SearchBoxBag, UseSearchBoxOptions } from "./headless/useSearchBox.js";
 export { RankingDisclosure } from "./headless/RankingDisclosure.js";
 export type { RankingDisclosureBag } from "./headless/RankingDisclosure.js";
 

package/src/model/queries.ts

@@ -6,7 +6,9 @@ import type {
   RankingResponse,
   SearchQueryState,
   SearchResponse,
+  SuggestResponse,
 } from "../api/types.js";
+import { SUGGEST_MAX_LIMIT, SUGGEST_MIN_CHARS } from "../state/limits.js";
 import { useSearchApi } from "./context.js";
 import { searchQueryKeys } from "./queryKeys.js";
 
@@ -60,6 +62,52 @@ export function useSearchQuery(
   });
 }
 
+/**
+ * Title prefixes from the index, for the search box's typeahead.
+ *
+ * Not from a query log: stapel-search keeps none, which is a privacy decision
+ * before it is a product one (`services.suggest`). So the list is what exists
+ * in the catalogue, and choosing one is always a search that has results.
+ *
+ * `enabled` is the debounce's partner, not its replacement: the CALLER holds a
+ * debounced prefix (see `useSearchBox`) and this hook refuses to ask about a
+ * prefix too short to mean anything. `placeholderData: keepPreviousData` keeps
+ * the previous list under the cursor while the next one is in flight — a menu
+ * that empties and refills on every keystroke is a menu nobody can click.
+ *
+ * `staleTime` is a minute: the index changes when something is published, not
+ * between two letters of one word.
+ */
+export function useSuggest(params: {
+  readonly type: string;
+  readonly q: string;
+  readonly limit?: number;
+  readonly enabled?: boolean;
+}): UseQueryResult<SuggestResponse, StapelApiError> {
+  const api = useSearchApi();
+  const q = params.q.trim();
+  const limit = params.limit;
+  return useQuery({
+    queryKey: searchQueryKeys.suggest(params.type, q, limit),
+    queryFn: ({ signal }) =>
+      api.suggest(
+        {
+          type: params.type,
+          q,
+          ...(limit !== undefined ? { limit: Math.min(limit, SUGGEST_MAX_LIMIT) } : {}),
+        },
+        { signal }
+      ),
+    enabled:
+      (params.enabled ?? true) &&
+      params.type.length > 0 &&
+      q.length >= SUGGEST_MIN_CHARS,
+    placeholderData: keepPreviousData,
+    staleTime: 60_000,
+    retry: false,
+  });
+}
+
 /**
  * The P2B Art. 5 ranking disclosure.
  *
@@ -67,12 +115,14 @@ export function useSearchQuery(
  * not while a person reads the page it explains.
  */
 export function useRankingDisclosure(
-  type?: string
+  type?: string,
+  options?: { readonly enabled?: boolean }
 ): UseQueryResult<RankingResponse, StapelApiError> {
   const api = useSearchApi();
   return useQuery({
     queryKey: searchQueryKeys.ranking(type),
     queryFn: ({ signal }) => api.ranking(type, { signal }),
+    enabled: options?.enabled ?? true,
     staleTime: Number.POSITIVE_INFINITY,
     retry: false,
   });

package/src/state/limits.ts

@@ -0,0 +1,50 @@
+/**
+ * The backend's own limits, in one place — and the two timings the client
+ * chooses so that it never provokes them.
+ *
+ * Every number here is a fact about stapel-search's `conf.py` (or, for the
+ * debounces, a decision taken because of one). They live in the state layer,
+ * beside the codec, because they are properties of the CONTRACT rather than of
+ * any component: a control that caps its input at `SEARCH_QUERY_MAX_CHARS`
+ * cannot produce `error.400.search_query_too_long`, and a typeahead that waits
+ * for `SEARCH_BOX_SUGGEST_DEBOUNCE_MS` does not earn a 429 from a throttled
+ * endpoint for typing quickly.
+ *
+ * They are DEFAULTS, not assertions: a deployment may raise `MAX_PAGE_SIZE` or
+ * lower `MAX_QUERY_CHARS`, and nothing here is sent to the server as a claim.
+ * The server remains the one entitled to refuse.
+ */
+
+/** `MAX_QUERY_CHARS` — the longest `q` (and suggest prefix) the server reads. */
+export const SEARCH_QUERY_MAX_CHARS = 200;
+
+/** `DEFAULT_PAGE_SIZE` — what a request with no `limit` gets. */
+export const SEARCH_DEFAULT_PAGE_SIZE = 24;
+
+/** `MAX_PAGE_SIZE` — the server clamps anything above this. */
+export const SEARCH_MAX_PAGE_SIZE = 100;
+
+/** `services.suggest` clamps `limit` into `1..25`. */
+export const SUGGEST_MAX_LIMIT = 25;
+
+/**
+ * The shortest prefix worth asking the index about.
+ *
+ * One and two letters match nearly everything, so the answer is noise and the
+ * request is a keystroke tax on a throttled endpoint (`SuggestThrottle`,
+ * scope `search-suggest`). Three is where a prefix starts to mean something.
+ */
+export const SUGGEST_MIN_CHARS = 3;
+
+/** How long the typing has to stop before the SEARCH runs. */
+export const SEARCH_BOX_DEBOUNCE_MS = 350;
+
+/**
+ * How long it has to stop before the INDEX is asked for prefixes.
+ *
+ * Shorter than the commit: a suggestion is only worth having while you are
+ * still typing, and it costs a cheap read of one column. Longer than zero: the
+ * endpoint is throttled per client, and a request per keystroke is how a person
+ * gets 429s for typing quickly.
+ */
+export const SEARCH_BOX_SUGGEST_DEBOUNCE_MS = 150;

package/src/state/ranges.ts

@@ -0,0 +1,144 @@
+/**
+ * The RANGE half of the filter model — `r.<slug>=from..to`.
+ *
+ * The codec has carried ranges since 0.1 (`setRangeValue`, `RANGE_PREFIX`) and
+ * nothing ever drew one: a marketplace shipped without a price filter because
+ * the panel only knew how to draw checkboxes. This module is the missing half:
+ * which slugs a range row exists for, and what the row is called.
+ *
+ * ── Where a range row comes from, and why it is not the response ───────────
+ *
+ * A facet answer (`facets: {slug: {value: count}}`) enumerates DISCRETE values;
+ * a range is not enumerable and the server never sends one. So the rows come
+ * from the CATEGORY SCHEMA — the same `categoryFeatures` slot that gives the
+ * checkboxes their labels — filtered to the numeric value types, plus every
+ * slug the URL already carries a range for.
+ *
+ * That last clause is the same rule `buildFacetGroups` follows for a filtered
+ * slug that fell out of the plan: a constraint that is ACTIVE must always have
+ * a control that removes it, even when the schema no longer explains it.
+ * Otherwise a shared link narrows the search with nothing on screen to widen it
+ * again.
+ *
+ * `date` is range-capable on the wire and is deliberately NOT here: a date
+ * range needs a date editor, the editor lives in `@stapel/attributes-react`'s
+ * registry, and a numeric input over a Unix timestamp would be worse than no
+ * control at all. The codec still round-trips one a host sets.
+ */
+import { featureConfig, featureName, featureType } from "@stapel/attributes-react";
+import type { FeatureDef } from "@stapel/attributes-react";
+import type { SearchQueryState, SearchRange } from "../api/types.js";
+
+/**
+ * Value types a numeric range row is drawn for (`config.type`, the
+ * stapel-attributes value-type slug).
+ */
+export const RANGE_FEATURE_TYPES: readonly string[] = [
+  "int",
+  "float",
+  "convertible_unit",
+];
+
+/** One `r.<slug>` row of the filter panel. */
+export interface RangeGroup {
+  readonly slug: string;
+  /** The feature's display name (translated when it is a key), else the slug. */
+  readonly label: string;
+  /** The schema entry behind the slug, when the host supplied one. */
+  readonly feature: FeatureDef | undefined;
+  /** The applied bounds, exactly as the URL carries them (strings — the wire
+   * never promised a number, and re-formatting one would rewrite the link). */
+  readonly from: string | undefined;
+  readonly to: string | undefined;
+  /** Bounds the schema declares, for the input's own limits. */
+  readonly min: number | undefined;
+  readonly max: number | undefined;
+  /** Unit suffix the schema declares (`postfix`, or a convertible unit). */
+  readonly unit: string | undefined;
+  /** `1` for an integer feature — a whole-number input for a whole number. */
+  readonly step: number | undefined;
+  /** Whether the URL currently constrains this slug. */
+  readonly active: boolean;
+}
+
+export interface BuildRangeGroupsInput {
+  readonly state: SearchQueryState;
+  readonly categoryFeatures?: readonly FeatureDef[];
+  /** Translator for label keys (the schema's `name` is often one). */
+  readonly t?: (key: string) => string;
+}
+
+function num(value: unknown): number | undefined {
+  return typeof value === "number" && Number.isFinite(value) ? value : undefined;
+}
+
+function str(value: unknown): string | undefined {
+  return typeof value === "string" && value.length > 0 ? value : undefined;
+}
+
+function translate(t: ((key: string) => string) | undefined, key: string): string {
+  if (t === undefined) return key;
+  const resolved = t(key);
+  return resolved.length > 0 ? resolved : key;
+}
+
+/** Is this feature one a numeric range row is drawn for? */
+export function isRangeFeature(feature: FeatureDef): boolean {
+  const type = featureType(feature);
+  return type !== undefined && RANGE_FEATURE_TYPES.includes(type);
+}
+
+/**
+ * The range rows for the current search: every numeric feature of the
+ * category, in the schema's own order, plus any slug the URL constrains that
+ * the schema does not explain.
+ */
+export function buildRangeGroups(
+  input: BuildRangeGroupsInput
+): readonly RangeGroup[] {
+  const bySlug = new Map<string, FeatureDef>();
+  for (const feature of input.categoryFeatures ?? []) bySlug.set(feature.slug, feature);
+
+  const slugs: string[] = [];
+  for (const feature of input.categoryFeatures ?? []) {
+    if (isRangeFeature(feature)) slugs.push(feature.slug);
+  }
+  for (const slug of Object.keys(input.state.ranges)) {
+    if (!slugs.includes(slug)) slugs.push(slug);
+  }
+
+  return slugs.map((slug) => {
+    const feature = bySlug.get(slug);
+    const config = feature === undefined ? {} : featureConfig(feature);
+    const applied: SearchRange | undefined = input.state.ranges[slug];
+    return {
+      slug,
+      label:
+        feature === undefined ? slug : translate(input.t, featureName(feature)),
+      feature,
+      from: applied?.from,
+      to: applied?.to,
+      min: num(config["min"]),
+      max: num(config["max"]),
+      unit: str(config["postfix"]) ?? str(config["unit_m"]) ?? str(config["unit_i"]),
+      step: feature !== undefined && featureType(feature) === "int" ? 1 : undefined,
+      active: applied !== undefined,
+    };
+  });
+}
+
+/**
+ * Is a from/to pair one the server could ever match?
+ *
+ * `100..50` is syntactically fine and semantically empty, and the backend does
+ * not refuse it — it answers zero results, which reads as "there is nothing
+ * like this" rather than "you typed it backwards". So the panel refuses to
+ * apply it and says why, beside the button (`search.facets.range_invalid`).
+ */
+export function isRangeUsable(range: SearchRange): boolean {
+  if (range.from === undefined || range.to === undefined) return true;
+  const from = Number(range.from);
+  const to = Number(range.to);
+  if (!Number.isFinite(from) || !Number.isFinite(to)) return true;
+  return from <= to;
+}

package/dist/default/ErrorAlert.d.ts

@@ -1,9 +0,0 @@
-import type { CSSProperties, ReactElement, ReactNode } from "react";
-import type { FlowErrorDisplay } from "@stapel/core";
-export declare function ErrorAlert(props: {
-    error: FlowErrorDisplay | undefined;
-    style?: CSSProperties | undefined;
-    testId?: string | undefined;
-    action?: ReactNode;
-}): ReactElement | null;
-//# sourceMappingURL=ErrorAlert.d.ts.map

package/dist/default/ErrorAlert.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"ErrorAlert.d.ts","sourceRoot":"","sources":["../../src/default/ErrorAlert.tsx"],"names":[],"mappings":"AAeA,OAAO,KAAK,EAAE,aAAa,EAAE,YAAY,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AACpE,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,cAAc,CAAC;AAErD,wBAAgB,UAAU,CAAC,KAAK,EAAE;IAChC,KAAK,EAAE,gBAAgB,GAAG,SAAS,CAAC;IACpC,KAAK,CAAC,EAAE,aAAa,GAAG,SAAS,CAAC;IAClC,MAAM,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;IAC5B,MAAM,CAAC,EAAE,SAAS,CAAC;CACpB,GAAG,YAAY,GAAG,IAAI,CAsBtB"}

package/dist/default/ErrorAlert.js

@@ -1,27 +0,0 @@
-import { jsx as _jsx } from "react/jsx-runtime";
-/**
- * The one error surface this pair's default skin renders, so the split copy
- * core produces reaches a screen the same way everywhere (mirrors the
- * docs/notifications/workspaces etalon).
- *
- * Core's `describeFlowError` splits a failure into the sentence a person
- * reads and the technical detail a support agent quotes (owner report
- * 2026-08-09: the status used to be spliced into the sentence, ending in a
- * bare `" (500)"`). The split only helps if a skin renders both halves at
- * their own weights: `message` at normal weight, `detail` muted and small.
- *
- * `undefined` in — including a `detail` core left `undefined` because there
- * was nothing worth quoting — renders nothing rather than an empty line.
- */
-import { Alert, Typography } from "antd";
-export function ErrorAlert(props) {
-    const { error } = props;
-    if (!error)
-        return null;
-    return (_jsx(Alert, { type: "error", showIcon: true, ...(props.style ? { style: props.style } : {}), ...(props.testId ? { "data-testid": props.testId } : {}), ...(props.action ? { action: props.action } : {}), message: error.message, ...(error.detail
-            ? {
-                description: (_jsx(Typography.Text, { type: "secondary", style: { fontSize: 12 }, children: error.detail })),
-            }
-            : {}) }));
-}
-//# sourceMappingURL=ErrorAlert.js.map

package/dist/default/ErrorAlert.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"ErrorAlert.js","sourceRoot":"","sources":["../../src/default/ErrorAlert.tsx"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;GAaG;AACH,OAAO,EAAE,KAAK,EAAE,UAAU,EAAE,MAAM,MAAM,CAAC;AAIzC,MAAM,UAAU,UAAU,CAAC,KAK1B;IACC,MAAM,EAAE,KAAK,EAAE,GAAG,KAAK,CAAC;IACxB,IAAI,CAAC,KAAK;QAAE,OAAO,IAAI,CAAC;IACxB,OAAO,CACL,KAAC,KAAK,IACJ,IAAI,EAAC,OAAO,EACZ,QAAQ,WACJ,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,KAAK,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,KAC3C,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,aAAa,EAAE,KAAK,CAAC,MAAM,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,KACrD,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,MAAM,EAAE,KAAK,CAAC,MAAM,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,EAClD,OAAO,EAAE,KAAK,CAAC,OAAO,KAClB,CAAC,KAAK,CAAC,MAAM;YACf,CAAC,CAAC;gBACE,WAAW,EAAE,CACX,KAAC,UAAU,CAAC,IAAI,IAAC,IAAI,EAAC,WAAW,EAAC,KAAK,EAAE,EAAE,QAAQ,EAAE,EAAE,EAAE,YACtD,KAAK,CAAC,MAAM,GACG,CACnB;aACF;YACH,CAAC,CAAC,EAAE,CAAC,GACP,CACH,CAAC;AACJ,CAAC"}

package/dist/default/theme.d.ts

@@ -1,24 +0,0 @@
-import type { CSSProperties, ReactElement, ReactNode } from "react";
-import type { ThemeMode } from "@stapel/tokens-antd";
-export interface SearchSkinThemeProps {
-    /**
-     * Light or dark. Defaults to the mode the host's document declares
-     * (`resolveThemeMode()`). Pass explicitly to pin a side.
-     */
-    readonly mode?: ThemeMode;
-    /** Extra styles merged onto the themed root element (layout only — colors
-     * come from the mode). */
-    readonly style?: CSSProperties;
-    readonly children: ReactNode;
-}
-/**
- * `<SearchSkinTheme/>` — the self-theming wrapper of
- * `@stapel/search-react/default`. Standalone use is supported (wrap any
- * composition of the skin's parts once); the shipped surfaces
- * (`SearchPage`, `SearchResultsPane`, `FacetPanelPane`,
- * `RankingDisclosurePane`) each already wrap themselves, and nested antd
- * `ConfigProvider`s merge, so composing them under one `SearchSkinTheme`
- * stays correct.
- */
-export declare function SearchSkinTheme(props: SearchSkinThemeProps): ReactElement;
-//# sourceMappingURL=theme.d.ts.map

package/dist/default/theme.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"theme.d.ts","sourceRoot":"","sources":["../../src/default/theme.tsx"],"names":[],"mappings":"AAgBA,OAAO,KAAK,EAAE,aAAa,EAAE,YAAY,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AAOpE,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,qBAAqB,CAAC;AAErD,MAAM,WAAW,oBAAoB;IACnC;;;OAGG;IACH,QAAQ,CAAC,IAAI,CAAC,EAAE,SAAS,CAAC;IAC1B;8BAC0B;IAC1B,QAAQ,CAAC,KAAK,CAAC,EAAE,aAAa,CAAC;IAC/B,QAAQ,CAAC,QAAQ,EAAE,SAAS,CAAC;CAC9B;AAED;;;;;;;;GAQG;AACH,wBAAgB,eAAe,CAAC,KAAK,EAAE,oBAAoB,GAAG,YAAY,CAmBzE"}

package/dist/default/theme.js

@@ -1,39 +0,0 @@
-import { jsx as _jsx } from "react/jsx-runtime";
-/**
- * The default skin's INTERNAL theme provider — every `/default` surface wraps
- * itself in this, so the skin is readable no matter what the host supplies
- * (tracker #26: a skin set with no internal provider once inherited a theme
- * bridge serving light-mode values inside a dark document — text on
- * background at 1.00:1). The theme derives from `@stapel/tokens` via
- * `@stapel/tokens-antd`'s `toAntdThemeConfig(mode)`; `mode` defaults to what
- * the HOST's document declares (`resolveThemeMode()` — the `data-theme`
- * attribute `tokens.css` keys its dark block on), never to a hardcoded side.
- *
- * This is also what "override styles" means for this pair: a storefront
- * retheming through the §68 token JSON regenerates its `--stapel-*` custom
- * properties and the result page follows with zero code — a far better deal
- * than a prop-per-colour API, and the reason the skin has none.
- */
-import { useMemo } from "react";
-import { ConfigProvider } from "antd";
-import { resolveThemeMode, toAntdTheme, toAntdThemeConfig, } from "@stapel/tokens-antd";
-/**
- * `<SearchSkinTheme/>` — the self-theming wrapper of
- * `@stapel/search-react/default`. Standalone use is supported (wrap any
- * composition of the skin's parts once); the shipped surfaces
- * (`SearchPage`, `SearchResultsPane`, `FacetPanelPane`,
- * `RankingDisclosurePane`) each already wrap themselves, and nested antd
- * `ConfigProvider`s merge, so composing them under one `SearchSkinTheme`
- * stays correct.
- */
-export function SearchSkinTheme(props) {
-    const mode = props.mode ?? resolveThemeMode();
-    const theme = useMemo(() => toAntdThemeConfig(mode), [mode]);
-    const token = useMemo(() => toAntdTheme(mode), [mode]);
-    return (_jsx(ConfigProvider, { theme: theme, children: _jsx("div", { "data-search-skin-root": true, "data-search-skin-mode": mode, style: {
-                color: token.colorText,
-                backgroundColor: token.colorBgContainer,
-                ...props.style,
-            }, children: props.children }) }));
-}
-//# sourceMappingURL=theme.js.map

package/dist/default/theme.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"theme.js","sourceRoot":"","sources":["../../src/default/theme.tsx"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;;GAcG;AACH,OAAO,EAAE,OAAO,EAAE,MAAM,OAAO,CAAC;AAEhC,OAAO,EAAE,cAAc,EAAE,MAAM,MAAM,CAAC;AACtC,OAAO,EACL,gBAAgB,EAChB,WAAW,EACX,iBAAiB,GAClB,MAAM,qBAAqB,CAAC;AAe7B;;;;;;;;GAQG;AACH,MAAM,UAAU,eAAe,CAAC,KAA2B;IACzD,MAAM,IAAI,GAAG,KAAK,CAAC,IAAI,IAAI,gBAAgB,EAAE,CAAC;IAC9C,MAAM,KAAK,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC,iBAAiB,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,CAAC,CAAC;IAC7D,MAAM,KAAK,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC,WAAW,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,CAAC,CAAC;IACvD,OAAO,CACL,KAAC,cAAc,IAAC,KAAK,EAAE,KAAK,YAC1B,sEAEyB,IAAI,EAC3B,KAAK,EAAE;gBACL,KAAK,EAAE,KAAK,CAAC,SAAS;gBACtB,eAAe,EAAE,KAAK,CAAC,gBAAgB;gBACvC,GAAG,KAAK,CAAC,KAAK;aACf,YAEA,KAAK,CAAC,QAAQ,GACX,GACS,CAClB,CAAC;AACJ,CAAC"}