MAIDR JavaScript API
    Preparing search index...

    Interface ChartJsDatasetMeta

    Metadata for a dataset (returned by chart.getDatasetMeta()).

    interface ChartJsDatasetMeta {
        data: ChartJsMetaElement[];
        type: string;
        vScale?: {
            id?: string;
            options?: { title?: { text?: string; display?: boolean } };
        };
        _parsed?: ChartJsParsedValue[];
        edges?: { source: ChartJsMetaElement; target: ChartJsMetaElement }[];
    }
    Index

    Properties

    type: string
    vScale?: {
        id?: string;
        options?: { title?: { text?: string; display?: boolean } };
    }

    The scale a dataset's values are measured against.

    chartjs-chart-pcp is why this is read: its controller gives every dataset its own axis and assigns it here, so a parallel coordinates chart's axes live on the metas rather than in chart.scales -- which holds only the one pcp category scale (#1184).

    _parsed?: ChartJsParsedValue[]

    What Chart.js parsed each of the dataset's values into.

    The distribution controllers are the ones that need it. A boxplot or a violin accepts either a raw array of samples or a pre-computed summary, and only this is the same shape for both -- the plugin does the quartile and density work here, so reading dataset.data sees the raw samples of the first form and nothing usable (#1049).

    edges?: { source: ChartJsMetaElement; target: ChartJsMetaElement }[]

    The links a chartjs-chart-graph controller drew, both ends resolved to the element that draws that node.

    The one uniform source: measured, this is filled for all three controllers and whether the author declared edges or left the plugin to derive them from parent. The ends are elements, so a reader pairs them back to node positions by identity against data.