import { type JsonApiVisualizationObjectInAttributesConditionalFormatting, type ConditionalFormatting as TigerConditionalFormatting } from "@gooddata/api-client-tiger";
import { type IConditionalFormatting, type IInsightDefinition } from "@gooddata/sdk-model";
/**
 * Projects the insight's conditional formatting (persisted free-form under
 * `properties.controls.conditionalFormatting`) into the typed visualizationObject entity attribute.
 *
 * Dual-write: `content` — which still carries the same rules inside `properties` — stays
 * authoritative; this typed attribute is a parallel, server-validated projection that readers switch
 * to later. Two boundary guarantees:
 * - Returns `null` (never `undefined`) when there is no formatting, so the PUT body explicitly clears
 *   the projection rather than relying on the server's omitted-attribute semantics — otherwise a
 *   cleared CF could leave a stale typed projection diverging from the authoritative `content`.
 * - A malformed blob (`content` is free-form and unvalidated) also degrades to `null`: the projection
 *   must never break a save, since `content` remains the source of truth. This includes a
 *   relative-date granularity tiger does not model.
 *
 * `version` and `suppressedTargets` are intentionally NOT carried — the typed schema does not model
 * them yet, and `content` stays authoritative until the switch, so nothing is lost. This is an
 * allow-list (see {@link convertConditionalFormattingToBackend}): a field added to
 * {@link IConditionalFormatting} will not auto-propagate; extend the shared mapping (and its test)
 * when the typed schema grows.
 */
export declare function convertConditionalFormatting(insight: IInsightDefinition): JsonApiVisualizationObjectInAttributesConditionalFormatting | null;
/**
 * Converts typed SDK conditional formatting into the tiger wire shape — the single mapping shared by
 * the visualizationObject entity attribute (see {@link convertConditionalFormatting}) and the tabular
 * export request. The mapping is a structural copy except for relative-date granularities, which the
 * SDK stores in its own vocabulary (`GDC.time.*`) while the wire uses tiger's (`YEAR`,
 * `MONTH_OF_YEAR`, ...); those are translated via the canonical granularity mapping.
 *
 * Throws `NotSupported` for a granularity tiger does not model — a caller feeding it untrusted data
 * must catch and degrade (the insight projection above turns it into `null`).
 */
export declare function convertConditionalFormattingToBackend(conditionalFormatting: IConditionalFormatting): TigerConditionalFormatting;
//# sourceMappingURL=ConditionalFormattingConverter.d.ts.map