@stapel/search-react 0.3.1 → 0.7.0

package/dist/state/degradations.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"degradations.d.ts","sourceRoot":"","sources":["../../src/state/degradations.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AACH,OAAO,KAAK,EAAE,iBAAiB,EAAE,qBAAqB,EAAE,MAAM,iBAAiB,CAAC;AAYhF,+CAA+C;AAC/C,wBAAgB,qBAAqB,CAAC,IAAI,EAAE,qBAAqB,GAAG,MAAM,CAEzE;AAED,0DAA0D;AAC1D,wBAAgB,iBAAiB,CAC/B,QAAQ,EAAE,SAAS,MAAM,EAAE,GAAG,SAAS,GACtC,SAAS,iBAAiB,EAAE,CAwB9B;AAED;;;;;;;GAOG;AACH,wBAAgB,eAAe,CAC7B,UAAU,EAAE,OAAO,EACnB,YAAY,EAAE,SAAS,iBAAiB,EAAE,GACzC,OAAO,CAET"}
+{"version":3,"file":"degradations.d.ts","sourceRoot":"","sources":["../../src/state/degradations.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AACH,OAAO,KAAK,EAAE,iBAAiB,EAAE,qBAAqB,EAAE,MAAM,iBAAiB,CAAC;AAYhF,+CAA+C;AAC/C,wBAAgB,qBAAqB,CAAC,IAAI,EAAE,qBAAqB,GAAG,MAAM,CAEzE;AAED,0DAA0D;AAC1D,wBAAgB,iBAAiB,CAC/B,QAAQ,EAAE,SAAS,MAAM,EAAE,GAAG,SAAS,GACtC,SAAS,iBAAiB,EAAE,CAwB9B;AAED;;;;;;;;;;;;GAYG;AACH,wBAAgB,eAAe,CAC7B,UAAU,EAAE,OAAO,EACnB,YAAY,EAAE,SAAS,iBAAiB,EAAE,GACzC,OAAO,CAET;AAED;;;;;;;GAOG;AACH,MAAM,MAAM,eAAe,GAAG,OAAO,GAAG,UAAU,GAAG,SAAS,CAAC;AAE/D;;;;;;;;;GASG;AACH,wBAAgB,SAAS,CACvB,KAAK,EAAE,MAAM,GAAG,IAAI,GAAG,SAAS,EAChC,YAAY,EAAE,OAAO,GAAG,SAAS,EACjC,UAAU,EAAE,OAAO,EACnB,YAAY,EAAE,SAAS,iBAAiB,EAAE,GACzC,eAAe,CAIjB;AAED;;;;;;;;;;;;;;GAcG;AACH,wBAAgB,iBAAiB,CAC/B,YAAY,EAAE,SAAS,iBAAiB,EAAE,GACzC,OAAO,CAKT"}

package/dist/state/degradations.js

@@ -45,8 +45,49 @@ export function parseDegradations(degraded) {
  * the envelope's own `exact_total: false`, and the `"exact_total"`
  * degradation. They agree in practice; treating either as decisive is what
  * keeps "≈1 200" from ever being rendered as "1 200".
+ *
+ * @deprecated Since stapel-search 0.2.0 the envelope answers this directly
+ * with `count_is_lower_bound`, and "not exact" now means a FLOOR rather than
+ * a fuzzy number. Use {@link countKind}, which reads the wire field and also
+ * handles `count: null`.
  */
 export function countIsEstimate(exactTotal, degradations) {
     return !exactTotal || degradations.some((d) => d.kind === "exact_total");
 }
+/**
+ * Read the envelope's three count fields as one decision.
+ *
+ * `null` is UNKNOWN and renders as no count line — never as `0`, and never
+ * as "about 0". Anything the server declines to call exact is rendered as a
+ * floor ("N+"), including the defensive case of an `exact_total: false` from
+ * a server that predates `count_is_lower_bound`: claiming "at least N" over
+ * a page that shows N rows is the one reading that cannot be contradicted by
+ * what the reader can see.
+ */
+export function countKind(count, isLowerBound, exactTotal, degradations) {
+    if (count === null || count === undefined)
+        return "unknown";
+    if (isLowerBound === true)
+        return "at_least";
+    return countIsEstimate(exactTotal, degradations) ? "at_least" : "exact";
+}
+/**
+ * Is `exact_total` the ONLY thing the engine could not do?
+ *
+ * It is a count NUANCE, not a failed search: the answer is complete, the
+ * rows are the right rows, and the single consequence — that the total is a
+ * floor — is already spoken by the count itself as "N+". Raising a warning
+ * banner over it teaches a reader that a perfectly good result page is
+ * broken, and a banner that cries wolf on every landing page is a banner
+ * nobody reads on the day `category_rollup` shows up in it.
+ *
+ * Every other degradation changes what the page MEANS ("typos were not
+ * corrected", "subcategories may be missing", "counts are approximate") and
+ * still renders. So does `exact_total` when it arrives BESIDE one of them —
+ * the list is then a description of a genuinely degraded answer.
+ */
+export function isCountNuanceOnly(degradations) {
+    return (degradations.length > 0 &&
+        degradations.every((degradation) => degradation.kind === "exact_total"));
+}
 //# sourceMappingURL=degradations.js.map

package/dist/state/degradations.js.map

@@ -1 +1 @@
-{"version":3,"file":"degradations.js","sourceRoot":"","sources":["../../src/state/degradations.ts"],"names":[],"mappings":"AAiBA,MAAM,aAAa,GAAG,SAAS,CAAC;AAEhC,MAAM,KAAK,GAAoD;IAC7D,cAAc,EAAE,gBAAgB;IAChC,eAAe,EAAE,iBAAiB;IAClC,WAAW,EAAE,aAAa;IAC1B,kBAAkB,EAAE,oBAAoB;IACxC,eAAe,EAAE,iBAAiB;CACnC,CAAC;AAEF,+CAA+C;AAC/C,MAAM,UAAU,qBAAqB,CAAC,IAA2B;IAC/D,OAAO,mBAAmB,IAAI,EAAE,CAAC;AACnC,CAAC;AAED,0DAA0D;AAC1D,MAAM,UAAU,iBAAiB,CAC/B,QAAuC;IAEvC,IAAI,QAAQ,KAAK,SAAS;QAAE,OAAO,EAAE,CAAC;IACtC,MAAM,IAAI,GAAG,IAAI,GAAG,EAAU,CAAC;IAC/B,MAAM,GAAG,GAAwB,EAAE,CAAC;IACpC,KAAK,MAAM,GAAG,IAAI,QAAQ,EAAE,CAAC;QAC3B,IAAI,IAAI,CAAC,GAAG,CAAC,GAAG,CAAC;YAAE,SAAS;QAC5B,IAAI,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;QACd,IAAI,GAAG,CAAC,UAAU,CAAC,aAAa,CAAC,EAAE,CAAC;YAClC,GAAG,CAAC,IAAI,CAAC;gBACP,IAAI,EAAE,QAAQ;gBACd,GAAG;gBACH,MAAM,EAAE,GAAG,CAAC,KAAK,CAAC,aAAa,CAAC,MAAM,CAAC;gBACvC,UAAU,EAAE,qBAAqB,CAAC,QAAQ,CAAC;aAC5C,CAAC,CAAC;YACH,SAAS;QACX,CAAC;QACD,MAAM,IAAI,GAAG,KAAK,CAAC,GAAG,CAAC,CAAC;QACxB,GAAG,CAAC,IAAI,CAAC;YACP,IAAI,EAAE,IAAI,IAAI,SAAS;YACvB,GAAG;YACH,UAAU,EAAE,qBAAqB,CAAC,IAAI,IAAI,SAAS,CAAC;SACrD,CAAC,CAAC;IACL,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,eAAe,CAC7B,UAAmB,EACnB,YAA0C;IAE1C,OAAO,CAAC,UAAU,IAAI,YAAY,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,aAAa,CAAC,CAAC;AAC3E,CAAC"}
+{"version":3,"file":"degradations.js","sourceRoot":"","sources":["../../src/state/degradations.ts"],"names":[],"mappings":"AAiBA,MAAM,aAAa,GAAG,SAAS,CAAC;AAEhC,MAAM,KAAK,GAAoD;IAC7D,cAAc,EAAE,gBAAgB;IAChC,eAAe,EAAE,iBAAiB;IAClC,WAAW,EAAE,aAAa;IAC1B,kBAAkB,EAAE,oBAAoB;IACxC,eAAe,EAAE,iBAAiB;CACnC,CAAC;AAEF,+CAA+C;AAC/C,MAAM,UAAU,qBAAqB,CAAC,IAA2B;IAC/D,OAAO,mBAAmB,IAAI,EAAE,CAAC;AACnC,CAAC;AAED,0DAA0D;AAC1D,MAAM,UAAU,iBAAiB,CAC/B,QAAuC;IAEvC,IAAI,QAAQ,KAAK,SAAS;QAAE,OAAO,EAAE,CAAC;IACtC,MAAM,IAAI,GAAG,IAAI,GAAG,EAAU,CAAC;IAC/B,MAAM,GAAG,GAAwB,EAAE,CAAC;IACpC,KAAK,MAAM,GAAG,IAAI,QAAQ,EAAE,CAAC;QAC3B,IAAI,IAAI,CAAC,GAAG,CAAC,GAAG,CAAC;YAAE,SAAS;QAC5B,IAAI,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;QACd,IAAI,GAAG,CAAC,UAAU,CAAC,aAAa,CAAC,EAAE,CAAC;YAClC,GAAG,CAAC,IAAI,CAAC;gBACP,IAAI,EAAE,QAAQ;gBACd,GAAG;gBACH,MAAM,EAAE,GAAG,CAAC,KAAK,CAAC,aAAa,CAAC,MAAM,CAAC;gBACvC,UAAU,EAAE,qBAAqB,CAAC,QAAQ,CAAC;aAC5C,CAAC,CAAC;YACH,SAAS;QACX,CAAC;QACD,MAAM,IAAI,GAAG,KAAK,CAAC,GAAG,CAAC,CAAC;QACxB,GAAG,CAAC,IAAI,CAAC;YACP,IAAI,EAAE,IAAI,IAAI,SAAS;YACvB,GAAG;YACH,UAAU,EAAE,qBAAqB,CAAC,IAAI,IAAI,SAAS,CAAC;SACrD,CAAC,CAAC;IACL,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,eAAe,CAC7B,UAAmB,EACnB,YAA0C;IAE1C,OAAO,CAAC,UAAU,IAAI,YAAY,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,aAAa,CAAC,CAAC;AAC3E,CAAC;AAYD;;;;;;;;;GASG;AACH,MAAM,UAAU,SAAS,CACvB,KAAgC,EAChC,YAAiC,EACjC,UAAmB,EACnB,YAA0C;IAE1C,IAAI,KAAK,KAAK,IAAI,IAAI,KAAK,KAAK,SAAS;QAAE,OAAO,SAAS,CAAC;IAC5D,IAAI,YAAY,KAAK,IAAI;QAAE,OAAO,UAAU,CAAC;IAC7C,OAAO,eAAe,CAAC,UAAU,EAAE,YAAY,CAAC,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,OAAO,CAAC;AAC1E,CAAC;AAED;;;;;;;;;;;;;;GAcG;AACH,MAAM,UAAU,iBAAiB,CAC/B,YAA0C;IAE1C,OAAO,CACL,YAAY,CAAC,MAAM,GAAG,CAAC;QACvB,YAAY,CAAC,KAAK,CAAC,CAAC,WAAW,EAAE,EAAE,CAAC,WAAW,CAAC,IAAI,KAAK,aAAa,CAAC,CACxE,CAAC;AACJ,CAAC"}

package/dist/state/limits.d.ts

@@ -0,0 +1,44 @@
+/**
+ * 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 declare const SEARCH_QUERY_MAX_CHARS = 200;
+/** `DEFAULT_PAGE_SIZE` — what a request with no `limit` gets. */
+export declare const SEARCH_DEFAULT_PAGE_SIZE = 24;
+/** `MAX_PAGE_SIZE` — the server clamps anything above this. */
+export declare const SEARCH_MAX_PAGE_SIZE = 100;
+/** `services.suggest` clamps `limit` into `1..25`. */
+export declare 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 declare const SUGGEST_MIN_CHARS = 3;
+/** How long the typing has to stop before the SEARCH runs. */
+export declare 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 declare const SEARCH_BOX_SUGGEST_DEBOUNCE_MS = 150;
+//# sourceMappingURL=limits.d.ts.map

package/dist/state/limits.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"limits.d.ts","sourceRoot":"","sources":["../../src/state/limits.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAEH,iFAAiF;AACjF,eAAO,MAAM,sBAAsB,MAAM,CAAC;AAE1C,iEAAiE;AACjE,eAAO,MAAM,wBAAwB,KAAK,CAAC;AAE3C,+DAA+D;AAC/D,eAAO,MAAM,oBAAoB,MAAM,CAAC;AAExC,sDAAsD;AACtD,eAAO,MAAM,iBAAiB,KAAK,CAAC;AAEpC;;;;;;GAMG;AACH,eAAO,MAAM,iBAAiB,IAAI,CAAC;AAEnC,8DAA8D;AAC9D,eAAO,MAAM,sBAAsB,MAAM,CAAC;AAE1C;;;;;;;GAOG;AACH,eAAO,MAAM,8BAA8B,MAAM,CAAC"}

package/dist/state/limits.js

@@ -0,0 +1,44 @@
+/**
+ * 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;
+//# sourceMappingURL=limits.js.map

package/dist/state/limits.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"limits.js","sourceRoot":"","sources":["../../src/state/limits.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAEH,iFAAiF;AACjF,MAAM,CAAC,MAAM,sBAAsB,GAAG,GAAG,CAAC;AAE1C,iEAAiE;AACjE,MAAM,CAAC,MAAM,wBAAwB,GAAG,EAAE,CAAC;AAE3C,+DAA+D;AAC/D,MAAM,CAAC,MAAM,oBAAoB,GAAG,GAAG,CAAC;AAExC,sDAAsD;AACtD,MAAM,CAAC,MAAM,iBAAiB,GAAG,EAAE,CAAC;AAEpC;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAAG,CAAC,CAAC;AAEnC,8DAA8D;AAC9D,MAAM,CAAC,MAAM,sBAAsB,GAAG,GAAG,CAAC;AAE1C;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,8BAA8B,GAAG,GAAG,CAAC"}

package/dist/state/ranges.d.ts

@@ -0,0 +1,52 @@
+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 declare const RANGE_FEATURE_TYPES: readonly string[];
+/** 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;
+}
+/** Is this feature one a numeric range row is drawn for? */
+export declare function isRangeFeature(feature: FeatureDef): boolean;
+/**
+ * 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 declare function buildRangeGroups(input: BuildRangeGroupsInput): readonly RangeGroup[];
+/**
+ * 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 declare function isRangeUsable(range: SearchRange): boolean;
+//# sourceMappingURL=ranges.d.ts.map

package/dist/state/ranges.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ranges.d.ts","sourceRoot":"","sources":["../../src/state/ranges.ts"],"names":[],"mappings":"AA4BA,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,0BAA0B,CAAC;AAC3D,OAAO,KAAK,EAAE,gBAAgB,EAAE,WAAW,EAAE,MAAM,iBAAiB,CAAC;AAErE;;;GAGG;AACH,eAAO,MAAM,mBAAmB,EAAE,SAAS,MAAM,EAIhD,CAAC;AAEF,8CAA8C;AAC9C,MAAM,WAAW,UAAU;IACzB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,+EAA+E;IAC/E,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,oEAAoE;IACpE,QAAQ,CAAC,OAAO,EAAE,UAAU,GAAG,SAAS,CAAC;IACzC;iFAC6E;IAC7E,QAAQ,CAAC,IAAI,EAAE,MAAM,GAAG,SAAS,CAAC;IAClC,QAAQ,CAAC,EAAE,EAAE,MAAM,GAAG,SAAS,CAAC;IAChC,8DAA8D;IAC9D,QAAQ,CAAC,GAAG,EAAE,MAAM,GAAG,SAAS,CAAC;IACjC,QAAQ,CAAC,GAAG,EAAE,MAAM,GAAG,SAAS,CAAC;IACjC,0EAA0E;IAC1E,QAAQ,CAAC,IAAI,EAAE,MAAM,GAAG,SAAS,CAAC;IAClC,4EAA4E;IAC5E,QAAQ,CAAC,IAAI,EAAE,MAAM,GAAG,SAAS,CAAC;IAClC,sDAAsD;IACtD,QAAQ,CAAC,MAAM,EAAE,OAAO,CAAC;CAC1B;AAED,MAAM,WAAW,qBAAqB;IACpC,QAAQ,CAAC,KAAK,EAAE,gBAAgB,CAAC;IACjC,QAAQ,CAAC,gBAAgB,CAAC,EAAE,SAAS,UAAU,EAAE,CAAC;IAClD,oEAAoE;IACpE,QAAQ,CAAC,CAAC,CAAC,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,MAAM,CAAC;CACtC;AAgBD,4DAA4D;AAC5D,wBAAgB,cAAc,CAAC,OAAO,EAAE,UAAU,GAAG,OAAO,CAG3D;AAED;;;;GAIG;AACH,wBAAgB,gBAAgB,CAC9B,KAAK,EAAE,qBAAqB,GAC3B,SAAS,UAAU,EAAE,CA8BvB;AAED;;;;;;;GAOG;AACH,wBAAgB,aAAa,CAAC,KAAK,EAAE,WAAW,GAAG,OAAO,CAMzD"}

package/dist/state/ranges.js

@@ -0,0 +1,108 @@
+/**
+ * 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";
+/**
+ * Value types a numeric range row is drawn for (`config.type`, the
+ * stapel-attributes value-type slug).
+ */
+export const RANGE_FEATURE_TYPES = [
+    "int",
+    "float",
+    "convertible_unit",
+];
+function num(value) {
+    return typeof value === "number" && Number.isFinite(value) ? value : undefined;
+}
+function str(value) {
+    return typeof value === "string" && value.length > 0 ? value : undefined;
+}
+function translate(t, key) {
+    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) {
+    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) {
+    const bySlug = new Map();
+    for (const feature of input.categoryFeatures ?? [])
+        bySlug.set(feature.slug, feature);
+    const slugs = [];
+    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 = 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) {
+    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;
+}
+//# sourceMappingURL=ranges.js.map

package/dist/state/ranges.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"ranges.js","sourceRoot":"","sources":["../../src/state/ranges.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AACH,OAAO,EAAE,aAAa,EAAE,WAAW,EAAE,WAAW,EAAE,MAAM,0BAA0B,CAAC;AAInF;;;GAGG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAsB;IACpD,KAAK;IACL,OAAO;IACP,kBAAkB;CACnB,CAAC;AA+BF,SAAS,GAAG,CAAC,KAAc;IACzB,OAAO,OAAO,KAAK,KAAK,QAAQ,IAAI,MAAM,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,SAAS,CAAC;AACjF,CAAC;AAED,SAAS,GAAG,CAAC,KAAc;IACzB,OAAO,OAAO,KAAK,KAAK,QAAQ,IAAI,KAAK,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,SAAS,CAAC;AAC3E,CAAC;AAED,SAAS,SAAS,CAAC,CAAwC,EAAE,GAAW;IACtE,IAAI,CAAC,KAAK,SAAS;QAAE,OAAO,GAAG,CAAC;IAChC,MAAM,QAAQ,GAAG,CAAC,CAAC,GAAG,CAAC,CAAC;IACxB,OAAO,QAAQ,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,GAAG,CAAC;AAC9C,CAAC;AAED,4DAA4D;AAC5D,MAAM,UAAU,cAAc,CAAC,OAAmB;IAChD,MAAM,IAAI,GAAG,WAAW,CAAC,OAAO,CAAC,CAAC;IAClC,OAAO,IAAI,KAAK,SAAS,IAAI,mBAAmB,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC;AAClE,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,gBAAgB,CAC9B,KAA4B;IAE5B,MAAM,MAAM,GAAG,IAAI,GAAG,EAAsB,CAAC;IAC7C,KAAK,MAAM,OAAO,IAAI,KAAK,CAAC,gBAAgB,IAAI,EAAE;QAAE,MAAM,CAAC,GAAG,CAAC,OAAO,CAAC,IAAI,EAAE,OAAO,CAAC,CAAC;IAEtF,MAAM,KAAK,GAAa,EAAE,CAAC;IAC3B,KAAK,MAAM,OAAO,IAAI,KAAK,CAAC,gBAAgB,IAAI,EAAE,EAAE,CAAC;QACnD,IAAI,cAAc,CAAC,OAAO,CAAC;YAAE,KAAK,CAAC,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;IACxD,CAAC;IACD,KAAK,MAAM,IAAI,IAAI,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,KAAK,CAAC,MAAM,CAAC,EAAE,CAAC;QACnD,IAAI,CAAC,KAAK,CAAC,QAAQ,CAAC,IAAI,CAAC;YAAE,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IAC9C,CAAC;IAED,OAAO,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE;QACxB,MAAM,OAAO,GAAG,MAAM,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QACjC,MAAM,MAAM,GAAG,OAAO,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,aAAa,CAAC,OAAO,CAAC,CAAC;QACnE,MAAM,OAAO,GAA4B,KAAK,CAAC,KAAK,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC;QAClE,OAAO;YACL,IAAI;YACJ,KAAK,EACH,OAAO,KAAK,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,SAAS,CAAC,KAAK,CAAC,CAAC,EAAE,WAAW,CAAC,OAAO,CAAC,CAAC;YACzE,OAAO;YACP,IAAI,EAAE,OAAO,EAAE,IAAI;YACnB,EAAE,EAAE,OAAO,EAAE,EAAE;YACf,GAAG,EAAE,GAAG,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;YACvB,GAAG,EAAE,GAAG,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;YACvB,IAAI,EAAE,GAAG,CAAC,MAAM,CAAC,SAAS,CAAC,CAAC,IAAI,GAAG,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC,IAAI,GAAG,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC;YAC9E,IAAI,EAAE,OAAO,KAAK,SAAS,IAAI,WAAW,CAAC,OAAO,CAAC,KAAK,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,SAAS;YAC7E,MAAM,EAAE,OAAO,KAAK,SAAS;SAC9B,CAAC;IACJ,CAAC,CAAC,CAAC;AACL,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,aAAa,CAAC,KAAkB;IAC9C,IAAI,KAAK,CAAC,IAAI,KAAK,SAAS,IAAI,KAAK,CAAC,EAAE,KAAK,SAAS;QAAE,OAAO,IAAI,CAAC;IACpE,MAAM,IAAI,GAAG,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;IAChC,MAAM,EAAE,GAAG,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC;IAC5B,IAAI,CAAC,MAAM,CAAC,QAAQ,CAAC,IAAI,CAAC,IAAI,CAAC,MAAM,CAAC,QAAQ,CAAC,EAAE,CAAC;QAAE,OAAO,IAAI,CAAC;IAChE,OAAO,IAAI,IAAI,EAAE,CAAC;AACpB,CAAC"}

package/llms.txt

@@ -1,6 +1,6 @@
-# @stapel/search-react 0.3.1
+# @stapel/search-react 0.7.0
 
-Headless React flow pair for stapel-search (contract >=0.1 <0.2) — business + state, zero visual opinion.
+Headless React flow pair for stapel-search (contract >=0.2 <0.3) — business + state, zero visual opinion.
 Built on @stapel/core: typed client + StapelApiError envelope, auth token refresh,
 verification-403 interception, i18n engine, analytics facade, TanStack Query layer.
 
@@ -30,6 +30,7 @@ Paths are relative to `/search/api/v1/`.
 ## Query hooks (server state; keys come only from the key factory)
 - useRankingDisclosure (query) → ranking
 - useSearchQuery (query) → query
+- useSuggest (query) → suggest
 
 ## Errors (render t(code, params); UX from remediation)
 54 keys (full catalog: manifest.json §errors). By remediation: fix_input 26 · retry 15 · verify 5 · wait_and_retry 5 · contact_support 2 · reauthenticate 1.
@@ -74,9 +75,19 @@ const { tracked } = useTracked();
 ```
 
 ## Demos (defineDemo → manifest.demos; compiled, linted, rendered examples)
-- search.facets → <FacetPanel> [default]  demo/FacetPanel.demo.tsx
-- search.ranking → <RankingDisclosure> [default]  demo/RankingDisclosure.demo.tsx
-- search.results → <SearchResults> [default]  demo/SearchResults.demo.tsx
+- search.box → <SearchBox> [empty|typed]  demo/SearchBox.demo.tsx
+- search.degradation-notice → <DegradationNotice> [banner|inline]  demo/DegradationNotice.demo.tsx
+- search.facet-panel-pane → <FacetPanelPane> [open-search|narrowed]  demo/FacetPanelPane.demo.tsx
+- search.filter-sheet → <SearchPage> [open]  demo/FilterSheet.demo.tsx
+- search.language-select → <LanguageSelect> [offered|from-a-link]  demo/LanguageSelect.demo.tsx
+- search.page → <SearchPage> [desktop|phone|unreadable-link]  demo/SearchPage.demo.tsx
+- search.page-size-select → <PageSizeSelect> [ladder|off-ladder]  demo/PageSizeSelect.demo.tsx
+- search.range-filter-row → <RangeFilterRow> [untouched|applied]  demo/RangeFilterRow.demo.tsx
+- search.ranking-pane → <RankingDisclosurePane> [desktop|phone]  demo/RankingDisclosurePane.demo.tsx
+- search.result-card → <SearchResultCard> [promoted|plain]  demo/SearchResultCard.demo.tsx
+- search.results-pane → <SearchResultsPane> [desktop|phone|empty]  demo/SearchResultsPane.demo.tsx
+- search.sort-select → <SortSelect> [no-centre|with-centre]  demo/SortSelect.demo.tsx
+- search.url-issue-notice → <UrlIssueNotice> [two-issues|one-issue]  demo/UrlIssueNotice.demo.tsx
 Each source file is the canonical usage snippet (open the default variant).
 
 ## Snippets