Member Junction
    Preparing search index...

    Interface StyleOverrides

    Styling a user explicitly asked for, carried on the spec as data rather than baked into generated code as color literals.

    The color slots each target a visualization surface whose colors are data-driven and therefore tolerant of light/dark mode — chart series and intensity ramps. Slots for mode-hostile surfaces (backgrounds, text, borders) are deliberately absent: honoring those safely requires derived per-mode variants.

    Hosts apply these over the theme-resolved tokens; components never read them. Invalid values are ignored rather than applied: an empty chartPalette, a sequentialScale with fewer than two stops, or a divergingScale missing either endpoint leaves the theme value in place.

    interface StyleOverrides {
        chartPalette?: string[];
        divergingScale?: { high: string; low: string; mid?: string };
        fontScale?: "small" | "normal" | "large";
        requestText?: string;
        sequentialScale?: string[];
        source: "user-request" | "organization-default";
    }
    Index

    Properties

    chartPalette? divergingScale? fontScale? requestText? sequentialScale? source

    Properties

    chartPalette?: string[]

    Categorical series colors, replacing ComponentStyles.chartPalette. e.g. a request for "blue and gold charts".

    divergingScale?: { high: string; low: string; mid?: string }

    Diverging ramp, replacing ComponentStyles.divergingScale. e.g. "a red-to-green heatmap".

    fontScale?: "small" | "normal" | "large"

    Uniform scale factor for the whole ComponentStyles.typography.fontSize ladder — 'small' tightens it to fit more on screen, 'large' opens it up for readability. 'normal' (and omitting the field) leaves the theme ladder alone.

    Scaling the tokens rather than asking a generator to pick different ones is what makes this reliable: every piece of text moves together, including text inside registry components and libraries the generator never touched.

    requestText?: string

    The wording that produced these values — the user's own words, or the organization setting they came from — for audit and so the intent survives regeneration.

    sequentialScale?: string[]

    Sequential intensity ramp (ordered light-to-dark), replacing ComponentStyles.sequentialScale. e.g. "shade the map in blues".

    source: "user-request" | "organization-default"

    Provenance of these values. Never a generator's own aesthetic choice — either the user asked for these colors explicitly, or they are the organization's standing visualization defaults applied by the generation pipeline.

    Advisory only: the host applies the color slots identically either way. It exists so tooling and generation gates can tell a specific request apart from a standing default, which are enforced differently.

    Settings

    Member Visibility

    On This Page

    Properties