@indxsearch/intrface 3.3.0 → 3.6.0

package/CHANGELOG.md

@@ -1,5 +1,37 @@
 # Changelog
 
+## 3.6.0
+
+### Minor Changes
+
+- 5ef6a54: `RangeFilterPanel` histogram bars are clickable. A click moves both slider thumbs onto that bar's bucket and applies it as the range filter; clicking the selected bucket again returns to the full range. Each bar is a button spanning the histogram's full height, so a one-pixel bar is as easy to hit as a tall one, with a hover tone, keyboard focus and an accessible label carrying the bucket's range and count.
+
+  The histogram's highlight also follows the thumbs exactly now. It used to light whole buckets, so with a coarse histogram the lit region overshot the selection by up to a bucket; the bars are now drawn muted with a lit copy clipped to the span between the thumbs, so a bucket the thumb sits in is lit up to the thumb and no further. The lit span is the selection only; what is still reachable under other filters stays on the slider track's live overlay, where it was.
+
+### Patch Changes
+
+- 7a83d42: `RangeFilterPanel` inputs no longer change width on decimal fields. The Min input's `max` attribute was `sliderValue - 1` with floating-point noise (`7.712999999999999` on a rating of 8.713), and the browser sizes a number input to the longest value its bounds admit, so Min came out three times wider than Max until the first drag. Bounds now go out rounded to the field's precision and one step apart instead of one unit, and both inputs carry an explicit width from the field's bounds, so the browser's guess never applies and a typed value is never clipped either.
+
+## 3.5.0
+
+### Minor Changes
+
+- b3a896a: One vocabulary for how the filter panels look. `control` replaces `displayType` on every panel and names the control each option renders as: `ValueFilterPanel` `checkbox | radio | button | toggle`, `BucketFilterPanel` `checkbox | radio | button`, `RangeFilterPanel` `slider | input`, `SortByPanel` `select | radio`. `displayType` still works as a deprecated alias (`'dropdown'` maps to `'select'`).
+
+  `radio` on the value and bucket panels is single-select: a click replaces the selection, and the field's other options keep their counts so the user can switch. `BucketFilterPanel` now hides buckets that hold no values, as the server hides zero-count facet values; `showEmpty` (replacing 3.4.0's `hideEmpty`) keeps them, disabled, for a fixed set of named buckets. It also gains `limit`, and `showActivePanel` now does something: it tints the panel while it holds a selection, on the value, bucket and range panels. `toggleFilter` and `toggleBucketFilter` take an optional `exclusive` flag for callers building their own single-select controls.
+
+## 3.4.0
+
+### Minor Changes
+
+- dcbbb78: New `BucketFilterPanel`: groups a numeric field into ranges the user can tick, several at once. Configure it with a bucket `width` (equal-width buckets over the field's range), an array of lower edges, or explicit `buckets` with labels and open ends. Each bucket is a range filter; buckets on one field are ORed and the field gets the same excluded-field facet search as `match="any"`, so the other buckets keep their counts after the first tick. Counts are summed client-side from the facet values, so no server change. `ActiveFiltersPanel` shows one chip per selected bucket, and `SearchState` gains `bucketFilters` with `toggleBucketFilter` / `resetBucketFilter` on the context.
+
+## 3.3.1
+
+### Patch Changes
+
+- b37653f: `<ValueFilterPanel match="any" />` now works on scalar fields. Facet counts came from the filtered search, which included the field's own selection, so on a field where every document holds one value ticking "red" left only red in the panel and the second value could never be picked. Each `any` field with a selection now gets a facets-only search whose filter leaves that field out, sent in parallel with the main search, and the panel reads that field's counts from it. Fields with nothing selected, and `match="all"` fields, send nothing extra.
+
 ## 3.3.0
 
 ### Minor Changes
@@ -7,7 +39,6 @@
 - Starting a search no longer sends `PUT …/datasets/{name}`. That is the server's create-or-open endpoint and needs write access, so every front-end had to ship a key that could change data. `SearchProvider` now calls only read endpoints (status, field lists, search, document lookup, filters), and works with a **Search only** API key. Servers without API key access levels are unaffected: the removed call returned 200 without doing anything for an existing dataset.
 - README: use a Search only key, limited to the front-end's datasets.
 
-
 ## 3.2.0
 
 ### Minor Changes

package/README.md

@@ -42,9 +42,9 @@ VITE_INDX_URL=https://your-indx-server.com
 VITE_INDX_TOKEN=your-bearer-token-here
 ```
 
-The token is an API key from the Indx console (Account → API keys). **Create it with the access level "Search only"**, limited to the team and the datasets this front-end searches. The key is sent from the browser, so anyone can read it; a Search key can search those datasets and nothing else, which is exactly what `SearchProvider` needs. Never use a Read or Full access key in a front-end — it would let anyone who opens the browser's network tab export or change your data.
+The token is an API key from the Indx console (Account → API keys). **Create it with the access level "Search only"**, limited to the team and the datasets this front-end searches. The key is sent from the browser, so anyone can read it; a Search key can search those datasets and nothing else, which is exactly what `SearchProvider` needs. Never use a Read or Full access key in a front-end. It would let anyone who opens the browser's network tab export or change your data.
 
-> Only the server URL and token come from the environment. Your **team** and **dataset** identify *what* you're searching, so they're passed directly as props on `SearchProvider` (shown below) — not as env vars.
+> Only the server URL and token come from the environment. Your **team** and **dataset** identify *what* you're searching, so they're passed directly as props on `SearchProvider` (shown below), not as env vars.
 
 **For local development:**
 ```bash
@@ -53,7 +53,7 @@ VITE_INDX_TOKEN=your-bearer-token-here
 ```
 
 **Security Notes:**
-- The key is visible to every visitor. Use a **Search only** key, limited to the datasets the page searches — Search keys need Indx server with API key access levels.
+- The key is visible to every visitor. Use a **Search only** key, limited to the datasets the page searches. Search keys need Indx server with API key access levels.
 - If a key with more access ever shipped in a page, revoke it in the console (Account → API keys); it stays valid until revoked or expired.
 - Never commit `.env.local` to version control.
 
@@ -224,7 +224,7 @@ import { ValueFilterPanel } from '@indxsearch/intrface';
   <ValueFilterPanel
     field="brand"
     label="Brand"
-    displayType="button"
+    control="button"
     layout="grid"
   />
 
@@ -247,6 +247,24 @@ import { RangeFilterPanel } from '@indxsearch/intrface';
 />
 ```
 
+### Bucket Filters (Numeric, grouped)
+
+Groups a numeric field into ranges the user can tick, several at once. Pick a bucket width, the lower edges, or spell the buckets out:
+
+```typescript
+import { BucketFilterPanel } from '@indxsearch/intrface';
+
+<BucketFilterPanel field="speed" label="Speed" width={20} />              // 0-19, 20-39, ... over the field's range
+<BucketFilterPanel field="speed" width={[1, 21, 41, 81, 181]} />         // 1-20, 21-40, 41-80, 81-180
+<BucketFilterPanel field="price" buckets={[
+  { label: 'Under 50', max: 49 },
+  { label: '50 to 199', min: 50, max: 199 },
+  { label: '200 and up', min: 200 },
+]} />
+```
+
+Each bucket is a range filter. Selected buckets on one field are ORed, so ticking two widens the result; across fields they AND as usual. Counts are summed from the field's facet values, so the field must be facetable for counts to show (filterable is enough for the filter itself).
+
 ### Active Filters Display
 
 ```typescript
@@ -283,9 +301,9 @@ export default function AdvancedSearch() {
         {/* Sidebar with filters */}
         <aside style={{ width: '250px' }}>
           <ActiveFiltersPanel />
-          <SortByPanel displayType="radio" />
+          <SortByPanel control="radio" />
           <ValueFilterPanel field="category" label="Category" />
-          <ValueFilterPanel field="brand" label="Brand" displayType="button" />
+          <ValueFilterPanel field="brand" label="Brand" control="button" />
           <RangeFilterPanel field="price" label="Price" />
         </aside>
 
@@ -322,7 +340,7 @@ export default function AdvancedSearch() {
 |------|------|----------|---------|-------------|
 | `url` | `string` | ✅ | - | INDX server URL |
 | `preAuthenticatedToken` | `string` | ✅ | - | Bearer token created on the Indx Dashboard |
-| `team` | `string` | ✅ | - | Team that owns the dataset — scopes requests to `/api/teams/{team}/datasets/{dataset}/…` |
+| `team` | `string` | ✅ | - | Team that owns the dataset, scoping requests to `/api/teams/{team}/datasets/{dataset}/…` |
 | `dataset` | `string` | ✅ | - | Dataset name |
 | `allowEmptySearch` | `boolean` | ❌ | `false` | Show results without query |
 | `enableFacets` | `boolean` | ❌ | `true` | Enable faceted search |
@@ -361,15 +379,16 @@ Initialisation failures (bad token, unknown dataset, unreachable server) and fai
 |------|------|---------|-------------|
 | `field` | `string` | ✅ | Field name to filter on |
 | `label` | `string` | ❌ | Display label |
-| `displayType` | `'checkbox' \| 'button' \| 'toggle'` | `'checkbox'` | Filter UI style |
+| `control` | `'checkbox' \| 'radio' \| 'button' \| 'toggle'` | `'checkbox'` | The control each value renders as. `radio` is single-select: a click replaces the selection and the other values keep their counts. `toggle` is for boolean fields. (`displayType` still works, deprecated) |
+| `showActivePanel` | `boolean` | `false` | Tint the panel while it has a selection |
 | `layout` | `'list' \| 'grid'` | `'list'` | Layout style |
 | `limit` | `number` | `undefined` | Max filters to show |
 | `startCollapsed` | `boolean` | `false` | Start collapsed |
 | `showCount` | `boolean` | `true` | Show facet counts |
 | `showNull` | `boolean` | `false` | List the `null` facet bucket (documents without the field) as an option |
-| `match` | `'all' \| 'any'` | `'all'` | How several selected values combine. `'all'` requires every selected value (right for multi-valued fields such as genres: each click narrows). `'any'` matches at least one (use on scalar fields, where a document holds a single value). |
+| `match` | `'all' \| 'any'` | `'all'` | How several selected values combine. `'all'` requires every selected value (right for multi-valued fields such as genres: each click narrows). `'any'` matches at least one (use on scalar fields, where a document holds a single value). An `any` field with a selection costs one extra facets-only search per query, so its other values keep their counts and stay selectable. |
 
-Different fields and range filters always narrow the result set (ANDed). With `displayType="toggle"` the field is treated as boolean whenever its facet keys are `true` / `false` / `null`, and the `null` bucket counts as `false`.
+Different fields and range filters always narrow the result set (ANDed). With `control="toggle"` the field is treated as boolean whenever its facet keys are `true` / `false` / `null`, and the `null` bucket counts as `false`.
 
 ### RangeFilterPanel Props
 
@@ -377,20 +396,40 @@ Different fields and range filters always narrow the result set (ANDed). With `d
 |------|------|----------|-------------|
 | `field` | `string` | ✅ | Field name to filter on |
 | `label` | `string` | ❌ | Display label |
-| `displayType` | `'slider' \| 'input'` | ❌ | Filter UI style (default `'input'`) |
+| `control` | `'slider' \| 'input'` | ❌ | Slider with inputs beneath, or inputs alone (default `'input'`; `displayType` still works, deprecated) |
+| `showActivePanel` | `boolean` | ❌ | Tint the panel while it has a selection (default `false`) |
 | `expectedMin` | `number` | ❌ | Expected lower bound (default `0`) |
 | `expectedMax` | `number` | ❌ | Expected upper bound (default `1000`) |
 | `step` | `number` | ❌ | Slider step. Derived from the precision of the field's values if omitted (1 for integers, 0.1 for one decimal, …) |
-| `showHistogram` | `boolean` | ❌ | Show a histogram above the slider (requires the field to be facetable; default `false`) |
+| `showHistogram` | `boolean` | ❌ | Show a histogram above the slider; clicking a bar filters on that bucket, clicking it again returns to the full range (requires the field to be facetable; default `false`) |
 | `resolution` | `number` | ❌ | Value-range per histogram bucket (e.g. `200` → 5 bars over 0–1000). Auto-derived (~20 bars) if omitted |
 | `collapsible` | `boolean` | ❌ | Whether the panel can collapse (default `true`) |
 | `startCollapsed` | `boolean` | ❌ | Start collapsed (default `false`) |
 
+### BucketFilterPanel Props
+
+| Prop | Type | Required | Description |
+|------|------|----------|-------------|
+| `field` | `string` | ✅ | Numeric field to filter on (must be filterable; facetable for counts) |
+| `label` | `string` | ❌ | Display label |
+| `width` | `number \| number[]` | ❌ | A number gives equal-width buckets aligned to multiples of it over the field's range. An array gives each bucket's lower edge, the last entry closing the final bucket. Ignored when `buckets` is set |
+| `buckets` | `{ label?, min?, max? }[]` | ❌ | Explicit buckets. Leave `min` or `max` off for an open end; it closes at the field's bound when sent |
+| `control` | `'checkbox' \| 'radio' \| 'button'` | ❌ | The control each bucket renders as; `radio` is single-select (default `'checkbox'`; `displayType` still works, deprecated) |
+| `limit` | `number` | ❌ | Buckets shown before a "Show more" button. Unlimited when omitted |
+| `showActivePanel` | `boolean` | ❌ | Tint the panel while it has a selection (default `false`) |
+| `layout` | `'list' \| 'grid'` | ❌ | Vertical list or wrapping grid (default `'list'`) |
+| `showCount` | `boolean` | ❌ | Show the document count per bucket (default `true`) |
+| `showEmpty` | `boolean` | ❌ | Keep buckets that hold no values, shown disabled. Off by default; the server never lists a zero-count value and buckets follow suit. Turn on for a fixed set of named buckets that should always be visible |
+| `collapsible` | `boolean` | ❌ | Whether the panel can collapse (default `true`) |
+| `startCollapsed` | `boolean` | ❌ | Start collapsed (default `false`) |
+
+Selected buckets on a field are always ORed (they are disjoint ranges). Like `ValueFilterPanel match="any"`, a field with a selection costs one extra facets-only search per query so the other buckets keep their counts.
+
 ### SortByPanel Props
 
 | Prop | Type | Default | Description |
 |------|------|---------|-------------|
-| `displayType` | `'dropdown' \| 'radio'` | `'dropdown'` | Sort UI style |
+| `control` | `'select' \| 'radio'` | `'select'` | A select, or one radio per option (`displayType` still works, deprecated; `'dropdown'` maps to `'select'`) |
 | `collapsible` | `boolean` | `true` | Allow the panel to collapse |
 | `startCollapsed` | `boolean` | `false` | Start collapsed |
 
@@ -436,7 +475,7 @@ import { useHybridSearch } from '@indxsearch/intrface';
 
 const { results, isLoading, error, search } = useHybridSearch(embeddingFn, {
   fieldName: 'embedding',
-  alpha: 0.5,       // optional, default 0.5 — blend of text vs. vector score
+  alpha: 0.5,       // optional, default 0.5, blend of text vs. vector score
   maxResults: 10,   // optional, default 10
   filter,           // optional FilterProxy
   timeoutMs,        // optional
@@ -450,11 +489,11 @@ await search('comfortable running shoes');
 
 These components are also exported and can be used for custom layouts:
 
-- `SearchResult` — a single result row; renders `children`, an optional index/score, and a skeleton state.
-- `SearchResultRow` — a lightweight row wrapper with `'title' | 'default'` variants for laying out result fields.
-- `SearchResultsSkeleton` — placeholder rows shown while results load (`rows` prop).
-- `FilterPanelSkeleton` — placeholder for a filter panel while facets load (`list` or `slider` variant).
-- `SearchSettingsPanel` — a ready-made panel for editing `searchSettings` (max results, coverage depth, placeholder text, coverage setup, etc.).
+- `SearchResult`: a single result row; renders `children`, an optional index/score, and a skeleton state.
+- `SearchResultRow`: a lightweight row wrapper with `'title' | 'default'` variants for laying out result fields.
+- `SearchResultsSkeleton`: placeholder rows shown while results load (`rows` prop).
+- `FilterPanelSkeleton`: placeholder for a filter panel while facets load (`list` or `slider` variant).
+- `SearchSettingsPanel`: a ready-made panel for editing `searchSettings` (max results, coverage depth, placeholder text, coverage setup, etc.).
 
 ## Troubleshooting
 
@@ -508,7 +547,7 @@ These components are also exported and can be used for custom layouts:
 
     <div className="filters">
       <ValueFilterPanel field="category" label="Category" />
-      <ValueFilterPanel field="brand" label="Brand" displayType="button" />
+      <ValueFilterPanel field="brand" label="Brand" control="button" />
       <RangeFilterPanel field="price" label="Price" expectedMin={0} expectedMax={1000} />
       <ValueFilterPanel field="inStock" label="In Stock" />
     </div>

package/dist/components/BucketFilterPanel.d.ts

@@ -0,0 +1,41 @@
+import { default as React } from 'react';
+/** A bucket the caller spells out. Leave `min` or `max` off for an open end. */
+export interface BucketSpec {
+    label?: string;
+    min?: number;
+    max?: number;
+}
+export interface BucketFilterPanelProps {
+    field: string;
+    label?: string;
+    /**
+     * Bucket width, or the lower edges of the buckets. A number gives equal-width
+     * buckets aligned to multiples of it across the field's range (width 20 on a
+     * 5-200 field: 0-19, 20-39, ... 180-199). An array gives the lower edge of
+     * each bucket, the last entry closing the final one: [1, 21, 41, 81, 181] is
+     * 1-20, 21-40, 41-80, 81-180. Ignored when `buckets` is given.
+     */
+    width?: number | number[];
+    /** Explicit buckets, optionally named and open-ended. Takes precedence over `width`. */
+    buckets?: BucketSpec[];
+    /** The control each bucket renders as. `radio` is single-select: a click replaces the selection. */
+    control?: 'checkbox' | 'radio' | 'button';
+    /** @deprecated Use `control`. */
+    displayType?: 'checkbox' | 'button';
+    layout?: 'list' | 'grid';
+    showCount?: boolean;
+    /**
+     * Keep buckets that hold no values, shown disabled. Off by default: the server
+     * never lists a facet value with a count of 0, and a bucket follows the same
+     * rule. Turn it on for a fixed set of named buckets that should always be
+     * visible, the way `preserveBlankFacetState` keeps a value panel's list stable.
+     */
+    showEmpty?: boolean;
+    /** Buckets shown before a "Show more" button. Unlimited when omitted. */
+    limit?: number;
+    /** Tint the panel while it has a selection. */
+    showActivePanel?: boolean;
+    collapsible?: boolean;
+    startCollapsed?: boolean;
+}
+export declare const BucketFilterPanel: React.FC<BucketFilterPanelProps>;

package/dist/components/FilterPanelSkeleton.d.ts

@@ -3,6 +3,8 @@ export interface FilterPanelSkeletonProps {
     title?: string;
     rows?: number;
     variant?: 'list' | 'slider';
+    /** Slider variant: reserve the histogram's row above the track, so a panel with `showHistogram` keeps its height when the data lands. */
+    withHistogram?: boolean;
     collapsible?: boolean;
     startCollapsed?: boolean;
 }

package/dist/components/RangeFilterPanel.d.ts

@@ -2,7 +2,11 @@ import { default as React } from 'react';
 export interface RangeFilterPanelProps {
     field: string;
     label?: string;
+    /** A two-thumb slider with inputs beneath, or the inputs alone. */
+    control?: 'slider' | 'input';
+    /** @deprecated Use `control`. */
     displayType?: 'slider' | 'input';
+    showActivePanel?: boolean;
     expectedMin?: number;
     expectedMax?: number;
     collapsible?: boolean;

package/dist/components/SortByPanel.d.ts

@@ -1,5 +1,8 @@
 import { default as React } from 'react';
 type SortByPanelProps = {
+    /** A select, or one radio per option. */
+    control?: 'select' | 'radio';
+    /** @deprecated Use `control`. `'dropdown'` maps to `'select'`. */
     displayType?: 'dropdown' | 'radio';
     collapsible?: boolean;
     startCollapsed?: boolean;

package/dist/components/ValueFilterPanel.d.ts

@@ -8,6 +8,13 @@ export interface ValueFilterPanelProps {
     limit?: number;
     collapsible?: boolean;
     startCollapsed?: boolean;
+    /**
+     * The control each value renders as. `radio` is single-select: a click replaces
+     * the selection, and the field's other values keep their counts so the user can
+     * switch. `toggle` is for boolean fields.
+     */
+    control?: 'checkbox' | 'radio' | 'button' | 'toggle';
+    /** @deprecated Use `control`. */
     displayType?: 'checkbox' | 'button' | 'toggle';
     layout?: 'list' | 'grid';
     showActivePanel?: boolean;

package/dist/context/SearchContext.d.ts

@@ -1,7 +1,7 @@
 import { default as React } from 'react';
 import { CoverageSetup } from '@indxsearch/indx-types';
-import { ValueMatch } from './buildFilterProxy';
-export type { ValueMatch };
+import { ValueMatch, NumericRange } from './buildFilterProxy';
+export type { ValueMatch, NumericRange };
 export type RequiredCoverageSetup = Required<CoverageSetup>;
 export interface SearchSettings {
     maxNumberOfRecordsToReturn: number;
@@ -35,6 +35,9 @@ export interface SearchState {
         min: number;
         max: number;
     }>;
+    bucketFilters: Record<string, NumericRange[]>;
+    fieldsSeeded: boolean;
+    filterRevision: number;
     facetStats?: Record<string, {
         min: number;
         max: number;
@@ -59,12 +62,14 @@ export interface SearchContextType {
     dataset: string;
     authenticatedFetch: (url: string, options?: RequestInit) => Promise<Response>;
     setQuery: (query: string) => void;
-    toggleFilter: (field: string, value: string) => void;
+    toggleFilter: (field: string, value: string, exclusive?: boolean) => void;
     setValueMatch: (field: string, match: ValueMatch) => void;
     setRangeFilter: (field: string, min: number, max: number) => void;
     resetFilters: () => void;
     resetSingleFilter: (field: string, value: string, isUserAction?: boolean) => void;
     resetRangeFilter: (field: string, isUserAction?: boolean) => void;
+    toggleBucketFilter: (field: string, range: NumericRange, exclusive?: boolean) => void;
+    resetBucketFilter: (field: string, range?: NumericRange, isUserAction?: boolean) => void;
     setSort: (field: string | null, ascending: boolean) => void;
     setDebounceDelay?: (ms: number) => void;
     setSearchSettings: (settings: Partial<SearchSettings>) => void;

package/dist/context/buildFilterProxy.d.ts

@@ -1,5 +1,9 @@
 type AuthenticatedFetch = (url: string, options?: RequestInit) => Promise<Response>;
 export type ValueMatch = 'all' | 'any';
+export interface NumericRange {
+    min: number;
+    max: number;
+}
 /**
  * Builds the server-side filter token for the current selection.
  *
@@ -7,12 +11,11 @@ export type ValueMatch = 'all' | 'any';
  * match mode: `'all'` (default) ANDs them — a document must carry every value,
  * which is the natural reading for multi-valued fields such as genres and
  * narrows the result set with each click; `'any'` ORs them, for scalar fields
- * where a document can only ever hold one of the values. The per-field results
- * are then ANDed with each other and with every range filter. Any failed
- * filter call throws — the caller must not fall back to an unfiltered search.
+ * where a document can only ever hold one of the values. Bucket filters (the
+ * ranges a BucketFilterPanel selects) are disjoint, so several on one field are
+ * always ORed. The per-field results are then ANDed with each other and with
+ * every range filter. Any failed filter call throws — the caller must not fall
+ * back to an unfiltered search.
  */
-export declare function buildFilterProxy(filters: Record<string, string[]>, rangeFilters: Record<string, {
-    min: number;
-    max: number;
-}>, url: string, team: string, dataset: string, authenticatedFetch: AuthenticatedFetch, valueMatch?: Record<string, ValueMatch>): Promise<any>;
+export declare function buildFilterProxy(filters: Record<string, string[]>, rangeFilters: Record<string, NumericRange>, url: string, team: string, dataset: string, authenticatedFetch: AuthenticatedFetch, valueMatch?: Record<string, ValueMatch>, bucketFilters?: Record<string, NumericRange[]>): Promise<any>;
 export {};

package/dist/context/useSearchExecution.d.ts

@@ -11,8 +11,7 @@ export interface UseSearchExecutionOptions {
     allowEmptySearch: boolean;
     facetsEnabled: boolean;
     enableDebugLogs: boolean;
-    filtersChangedByUser: React.MutableRefObject<boolean>;
     shouldFetchMore: React.MutableRefObject<boolean>;
 }
 export type UseSearchExecutionResult = void;
-export declare function useSearchExecution({ state, setState, authenticatedFetch, auth, url, team, dataset, allowEmptySearch, facetsEnabled, enableDebugLogs, filtersChangedByUser, shouldFetchMore, }: UseSearchExecutionOptions): UseSearchExecutionResult;
+export declare function useSearchExecution({ state, setState, authenticatedFetch, auth, url, team, dataset, allowEmptySearch, facetsEnabled, enableDebugLogs, shouldFetchMore, }: UseSearchExecutionOptions): UseSearchExecutionResult;