tableToChartJS

• TableToChartJS.xml: a wiki macro of the XAR, with no content, whose Velocity code reads the table of the page by its id and calls the chartjs macro with the same type, options, width, height, cssClass, title and id, and declares no inline support.
• Chart.js Integration: the legacy documentation page of both macros of the extension, the only documentation of the parameters.
• ChartJS macro audit: the other macro of the extension, audited at the same time, whose ratings for what the two share are kept the same.

C1, minor: "The type of chart. Choose from: line, bar, radar, pie, doughnut, polarArea, bubble, scatter." says what it sets and gives the values, but the list is presented as complete while the horizontalBar of the last example of the documentation works and is not in it, and the values are the Chart.js identifiers, written as is, with the case that matters, see E2.

C2: mandatory, while a default type, like bar, would work for the table of the most common example and for any table of the documentation: {{tableToChartJS table="singleDataSet" /}} would give a chart instead of the error "Parameter [type] is mandatory". Because of it, Quick Actions opens the Edit Macro dialog, see L1.

C4: a free text field, although the accepted values are a short list of chart types: a select, ideally with a preview of each type, could be used. type="unknownChart" and type="polararea" are accepted and draw nothing, see E2.

C5: outside any group, with table, so 2 fields, and the Optional parameters group comes after.

C6: second of the dialog, after table, and set by the most common example, which sets only table and type.

C13: the accepted values are a list rather than a format, so it is recorded N/A: the select of C4 would declare them.

C1, minor: "Whether the specified table includes multiple data sets." uses a Chart.js term and does not say what the table must look like: the first column holds the labels and each other column is one data set, with the header cell as its name. Four of the five examples need it, since they have two data columns.

C3: the box is unchecked, the declared default false, the value of the most common example.

C4: a checkbox for a boolean.

C5, minor: the 8 fields of the Optional parameters group are above 7, mixing the options of the data, multipleDataSets and dataSetLabel, with the display options, width, height, cssClass, title and id. The same holds for every parameter of the group.

C6: fifth of the Optional parameters group, in alphabetical order, below cssClass, dataSetLabel, height and id, but visible without scrolling, and not set by the most common example.

C8: set by four of the five examples of the documentation, so not rarely used.

C1: "Identifies the source table." does not say what to type: the id of a table of the same page, which has to be set on the table first, see D2. It gives no possible value for a free field. To reproduce: open the Edit Macro dialog from Quick Actions.

C2: mandatory, since the macro cannot guess which table of the page to draw.

C4: a free text field for a reference to an element of the page, where a picker listing the tables of the page that have an id could be used. A misspelled id gives an empty chart with no message, see E2.

C5: outside any group, with type, so 2 fields.

C6: first of the dialog, with the focus, and set by the most common example.

C1: "The index of the table column that represents the data set label." does not say that it only has an effect together with multipleDataSets, nor where the index starts: the last example sets "1" for a table whose second column, Project, holds the label, so it starts at 0. It uses developer terms, index and data set.

C3: the field opens empty, which stands for no label column, the value of the most common example.

C4: a plain text field for a column number, which a number field, or a select of the columns of the table, would fit.

C5, minor: the 8 fields of the Optional parameters group are above 7, see the note of multipleDataSets.

C6: third of the group, not set by the most common example.

C8, minor: set by one of the five examples, and only useful for a table with a label column among its data columns.

C13: a column number with no declared range, and the macro is a wiki macro, whose parameters cannot declare a range or a format, see XWIKI-25197 in the Cross-macro findings. dataSetLabel="abc" is ignored, and dataSetLabel="9" draws empty bars with a nameless legend, see E2.

C1: "Advanced chart options specified as JSON. Checkout the Chart.js documentation for the available configuration options." gives the format and where the keys are listed. The keys that the macro adds, like backgroundColors, are not named, they are on the documentation page of the chartjs macro.

C3: the field opens empty, for the default options of Chart.js, the value of the most common example.

C4: a one line text field for a JSON object. A custom picker for this mini-syntax would be overkill, so the text field is OK, as long as the description explains the format, which it does.

C5, minor: the 8 fields of the Optional parameters group are above 7, see the note of multipleDataSets.

C6: sixth of the group, not set by the most common example.

C8: the description itself says "Advanced", and the field is not marked advanced, while only the last example of five sets it.

C13: a JSON format that the macro cannot declare, since the parameters of a wiki macro cannot declare a format, see XWIKI-25197 in the Cross-macro findings. options="{not json" is accepted and ignored, see E2.

C1: "Width of the generated chart." gives no unit and does not say that it has no visible effect with the default options. The name is the ID, "width", and the description is not translated in French and German. To reproduce: open the Edit Macro dialog from Quick Actions.

C3: the field opens empty, which stands for the width of the parent, the value of the most common example.

C4: a plain text field for a number of pixels, the value of the width attribute of the canvas.

C5, minor: the 8 fields of the Optional parameters group are above 7, see the note of multipleDataSets. The field is the last of the dialog, below the fold.

C6: last of the group, not set by the most common example.

C8: not marked advanced, and with the default options it changes nothing: width="300" is written on the canvas, which Chart.js resizes to the width of its container, 803 pixels in the audit. It only applies with options='{"responsive": false}' .

C13: a number of pixels with no declared range, and the parameters of a wiki macro cannot declare one, see XWIKI-25197 in the Cross-macro findings. width="abc" is accepted, see E2.

C1: "Height of the generated chart." gives no unit and does not say that it has no visible effect with the default options. The name is the ID, "height", and the description is not translated in French and German. The test page of the extension itself sets height="200px" , which is not a number of pixels.

C3: the field opens empty, which stands for the height that Chart.js computes from the width, the value of the most common example.

C4: a plain text field for a number of pixels, the value of the height attribute of the canvas.

C5, minor: the 8 fields of the Optional parameters group are above 7, see the note of multipleDataSets.

C6: third of the group, not set by the most common example.

C8: not marked advanced, and with the default options it changes nothing: height="150" is overridden by the aspect ratio of Chart.js. It only applies with options='{"maintainAspectRatio": false}' , where the height is then 150 pixels, or with responsive set to false in the options.

C13: a number of pixels with no declared range, and the parameters of a wiki macro cannot declare one, see XWIKI-25197 in the Cross-macro findings. height="-3" is accepted, see E2.

C1: "Additional CSS class to be added to the chart container." is a technical term for a styling hook, which another wording would only make more confusing. The name is the ID and the description is not translated in French and German.

C4: a text field for CSS classes, which is the usual input for a styling hook.

C5, minor: the 8 fields of the Optional parameters group are above 7, see the note of multipleDataSets.

C6: first of the group, not set by the most common example.

C8: a rarely used styling hook, not marked advanced.

C1: "Chart title, added as aria-label to the generated canvas" uses developer terms, and the name suggests a title drawn on the chart, like the title of the Chart macro of XWiki Standard, while it is only the text alternative of the canvas, which no title is drawn from. The meaning is clear once read, so the KO is minor. The name is the ID and the description is not translated in French and German.

C3: the field opens empty, for no text alternative, the value of the most common example. A chart with no title has an img role and no name.

C5, minor: the 8 fields of the Optional parameters group are above 7, see the note of multipleDataSets. The field is below the fold.

C6: seventh of the group, not set by the most common example.

C8: the only text alternative of a chart that screen readers cannot read, so it is not a rarely used parameter, even if the examples do not set it.

C1: "Chart identifier" is a technical term for a hook, the id of the canvas, which another wording would only make more confusing. The name is the ID and the description is not translated in French and German.

C5, minor: the 8 fields of the Optional parameters group are above 7, see the note of multipleDataSets.

C6: fourth of the group, not set by the most common example.

C8: a rarely used hook, not marked advanced.

C13: an HTML id has no space and is unique in the page, a format that the macro cannot declare, since the parameters of a wiki macro cannot declare one, see XWIKI-25197 in the Cross-macro findings. id="my chart" is accepted and written on the canvas as given, an invalid id, see E2.