kapom-report - v0.1.2
    Preparing search index...

    Interface KapomBlocksConfig<T>

    Full layer 3: pass a ReportNode tree directly (text/stack/section/signature/table freely mixed, including a SectionNode[] from ReportRegistry.build) — the facade still wires up jsPDF/RenderEngine/finalize exactly like the single-table config, just without composing the tree for you.

    interface KapomBlocksConfig<T = unknown> {
        blocks: readonly ReportNodeInput<T>[];
        document?: jsPDFOptions;
        font?: FontConfig;
        margins?: Partial<PageMargins>;
        numeric?: NumericStrategy;
        pageFooter?: KapomPageBandInput;
        pageHeader?: KapomPageBandInput;
        pageNumber?: PageNumberInput;
        theme?: ThemeInput;
        typography?: DeepPartial<Typography>;
        watermark?: WatermarkInput;
    }

    Type Parameters

    • T = unknown

    Hierarchy (View Summary)

    Index
    blocks: readonly ReportNodeInput<T>[]

    also accepts text shorthand — a plain string, or { content, role?, style? } without type, is a text node

    document?: jsPDFOptions

    passed straight into new jsPDF(options) — orientation/format/unit etc. (omit = jsPDF's own default, a4/portrait/mm)

    font?: FontConfig
    margins?: Partial<PageMargins>
    numeric?: NumericStrategy
    pageFooter?: KapomPageBandInput
    pageHeader?: KapomPageBandInput
    pageNumber?: PageNumberInput

    a lightweight page-number annotation drawn inside the page margin — doesn't reduce content area (unlike pageHeader/pageFooter); true for the default (bottom-left), a position string, or a full object

    theme?: ThemeInput

    ready-made colour scheme (preset name or a Theme object) — drives every table fill; omit = the default blue/grey look

    typography?: DeepPartial<Typography>
    watermark?: WatermarkInput

    a preset { text: 'DRAFT', ... } or a full render callback (escape hatch)