@perspective-dev/viewer
    Preparing search index...

    A numeric column's number_format (columns_config value) — Intl.NumberFormat-shaped options, written by the Style tab's number format editor and read by createNumberFormatter. The style and notation families ([NumberFormatStyle] / [Notation]) are serde- FLATTENED into this object but #[ts(skip)]'d (ts-rs cannot flatten Option<enum>) — the package's NumberFormatConfig re-composes the full wire type as CustomNumberFormatConfig & Partial<NumberFormatStyle> & Partial<Notation> (see column-format.ts).

    type CustomNumberFormatConfig = {
        maximumFractionDigits?: number | null;
        maximumSignificantDigits?: number | null;
        minimumFractionDigits?: number | null;
        minimumIntegerDigits?: number | null;
        minimumSignificantDigits?: number | null;
        roundingIncrement?: number | null;
        roundingMode?: RoundingMode | null;
        roundingPriority?: RoundingPriority | null;
        signDisplay?: SignDisplay | null;
        trailingZeroDisplay?: TrailingZeroDisplay | null;
        useGrouping?: UseGrouping | null;
    }
    Index

    Properties

    maximumFractionDigits?: number | null
    maximumSignificantDigits?: number | null
    minimumFractionDigits?: number | null
    minimumIntegerDigits?: number | null
    minimumSignificantDigits?: number | null
    roundingIncrement?: number | null
    roundingMode?: RoundingMode | null
    roundingPriority?: RoundingPriority | null
    signDisplay?: SignDisplay | null
    trailingZeroDisplay?: TrailingZeroDisplay | null
    useGrouping?: UseGrouping | null

    NOTE (audit 2026-08-05): serialized values are the STRINGS "always"/"auto"/"min2" or the untagged BOOLEAN false — the former hand-written TS useGrouping?: boolean was wrong for the string cases.