import type { ReactiveController, ReactiveControllerHost } from 'lit';
/**
 * Serialize a RoxyAPI response for embedding inside an inline `<script type="application/json" class="roxy-data">`. This is the safe writer counterpart to {@link MarkupDataController}, the reader: server-rendered and cached consumers (WordPress, JSX SSR, static HTML) emit the script with this, and the component hydrates `data` from it on connect.
 *
 * @remarks
 * Use this instead of a bare `JSON.stringify`. A raw stringify of a response that contains the literal text `</script>` (common in long interpretation prose) closes the script element early, corrupting the page and creating an HTML-injection vector. This escapes the script-unsafe characters to their `\uXXXX` JSON escapes, which `JSON.parse` restores to the original characters, so the value the component receives is identical to the response you passed.
 *
 * `<` is the load-bearing escape (it defeats `</script>` and `<!--`). `>` and `&` are escaped for defence in depth, and U+2028 / U+2029 because they are valid in JSON yet are line terminators in a `<script>` context and break some parsers. The escapes introduce only `\uXXXX` sequences, so the replacements never feed each other and order is irrelevant.
 *
 * Pass the unwrapped RoxyAPI response, the same shape you would assign to `element.data`. Do not pass the SDK envelope (`{ data, error, request, response }`).
 *
 * @example
 * ```ts
 * import { serializeRoxyData } from '@roxyapi/ui';
 *
 * const { data } = await roxy.dreams.getDreamSymbol({ path: { id: 'water' } });
 * const html = `<roxy-dream-card><script type="application/json" class="roxy-data">${serializeRoxyData(data)}</script></roxy-dream-card>`;
 * ```
 */
export declare function serializeRoxyData(data: unknown): string;
/**
 * Build the complete `<script type="application/json" class="roxy-data">…</script>` element a server nests inside a `roxy-*` component for the no-JavaScript hydration path. The payload is escaped via {@link serializeRoxyData}, so it is safe to drop straight into HTML output.
 *
 * @remarks
 * The element carries both `type="application/json"` and `class="roxy-data"` because {@link MarkupDataController} reads only a direct-child script that has both. Emit one of these inside the target component; the JavaScript `data` property still wins if it is later assigned.
 *
 * @example
 * ```ts
 * import { roxyDataScript } from '@roxyapi/ui';
 *
 * const { data } = await roxy.crystals.getCrystal({ path: { id: 'amethyst' } });
 * const html = `<roxy-crystal-grid>${roxyDataScript(data)}</roxy-crystal-grid>`;
 * ```
 */
export declare function roxyDataScript(data: unknown): string;
/**
 * Host shape the controller drives: any reactive element that exposes a public `data` slot. The controller only writes `data` when the host left it unset, so the JavaScript property path always wins.
 */
interface DataHost extends ReactiveControllerHost, HTMLElement {
    data?: unknown;
}
/**
 * Reactive controller that lets a component hydrate its `data` from embedded markup when no `data` property was assigned in JavaScript.
 *
 * @remarks
 * The server-side and cached-render model: a backend renders the RoxyAPI response into a direct-child `<script type="application/json" class="roxy-data">` element, ships static HTML, and never runs per-element JavaScript to assign a property. On connect this controller reads that script, parses it, and feeds the result to the host. The JavaScript property path is untouched and authoritative: if `host.data` already holds a value when the host connects, the controller does nothing and the markup is ignored.
 *
 * Source resolution order on connect, first hit wins:
 *
 * 1. `host.data` already set in JavaScript -> leave it, read nothing.
 * 2. A direct-child `<script type="application/json" class="roxy-data">` -> parse and use. Direct-child only, so a nested component's own script is never read by an ancestor.
 *
 * Fetching from a URL is intentionally unsupported: that would require a browser-visible key and breaks the server-rendered, cached model these consumers rely on.
 *
 * Timing: {@link hostConnected} runs inside the host `connectedCallback`. For an element parsed from server HTML, its direct children are present by the time the custom element upgrades and connects, so the script is readable here. For an element created with `document.createElement` and connected before any child is appended, there is nothing to read and the property path is the only source, which is exactly the existing behavior.
 *
 * Failure is safe: malformed JSON or a missing script leaves `host.data` untouched, so the host renders its normal empty state.
 *
 * Reading the script never mutates it, and only the marked script is touched, so any sibling fallback markup a server nested inside the element (for no-JavaScript, AMP, or crawler rendering) is left in place.
 *
 * @example
 * ```ts
 * import { MarkupDataController } from '../utils/markup-data.js';
 *
 * export class RoxyExample extends LitElement {
 *   constructor() {
 *     super();
 *     new MarkupDataController(this);
 *   }
 *
 *   @property({ attribute: false })
 *   data: ExampleResponse | null = null;
 * }
 * ```
 */
export declare class MarkupDataController<T = unknown> implements ReactiveController {
    private readonly host;
    constructor(host: DataHost);
    hostConnected(): void;
    /**
     * Resolve the embedded payload. Returns `undefined` when there is nothing valid to read so the caller can leave `host.data` untouched.
     */
    private read;
    /**
     * Direct-child `<script type="application/json" class="roxy-data">`. Scoped to immediate children so a nested data-driven component never has its script read by an ancestor, and so sibling fallback markup is ignored.
     */
    private findInlineScript;
    private parse;
}
export {};
//# sourceMappingURL=markup-data.d.ts.map