import type { FuseResult } from 'fuse.js';
import type { GetItemKeys } from '../types/utils';
/**
 * Escapes a full-text-search snippet to safe HTML, keeping its `<mark>` tags.
 *
 * Everything else in `snippet` is escaped, so a value carrying `<script>`
 * renders as text. The preserved tag is hardcoded on purpose: taking it as a
 * parameter would let a caller pass any tag through to the `v-html` that renders
 * the result.
 *
 * Splitting on the tag is what makes that hold. The previous version swapped the
 * tags for `\0markO\0`/`\0markC\0`, escaped, then swapped back — and NUL is an
 * ordinary character a snippet can carry, so what decided whether markup was
 * emitted was a string the input could supply (#391).
 *
 * A whole sentinel in the input forged a tag outright. Worse, and easier: six of
 * its seven bytes immediately before a *real* tag were enough, because the
 * placeholder this function inserted for that tag completed the prefix. So
 * `\0markO<mark>` came back as `<mark>markO\0` — the genuine highlight moved to
 * the front of the text it was meant to mark. No crafted sequence, one stray
 * fragment ahead of any highlight.
 *
 * @param snippet Snippet from the search index, with `<mark>` marking the hits.
 * @returns HTML safe to render, with the highlight tags intact.
 */
export declare function sanitizeSnippet(snippet: string): string;
/**
 * Wraps a Fuse match in `<mark>` and trims the text before it, as HTML.
 *
 * Returns `undefined` when nothing here applies to the item: when it carries no
 * matches at all — Fuse only populates them when `includeMatches` is set, which
 * `ContentSearch` does by default and `CommandPalette` leaves to the caller —
 * and equally when `forceKey` names a key none of the matches is on, or
 * `omitKeys` covers every one of them. Callers render the plain value in that
 * case. Everything except the inserted tags is escaped; the result is rendered
 * with `v-html`.
 *
 * Text before the match is dropped when it does not fit, leaving an ellipsis, so
 * the highlight stays visible in a narrow row. Both boundaries land on whole
 * characters as a reader counts them, never inside an emoji or a flag.
 *
 * @param item Search result; its `matches` come from Fuse.
 * @param searchTerm The query, used as the length threshold a match must reach.
 * @param forceKey Consider only the match on this key.
 * @param omitKeys Skip matches on these keys — used to keep a hit from being
 * highlighted twice across label, suffix and description.
 * @param useTokenSearch Measure the threshold against the shortest word of the
 * query instead of the whole of it, so multi-word queries highlight each word.
 * b24ui-only, and not present upstream — see `.sync/PORTING.md` §2.
 * @returns The escaped HTML, or `undefined` when there is nothing to highlight.
 */
export declare function highlight<T>(item: T & {
    matches?: FuseResult<T>['matches'];
}, searchTerm: string, forceKey?: GetItemKeys<T>, omitKeys?: GetItemKeys<T>[], useTokenSearch?: boolean): string | undefined;