script

• Script macro base class source code: the macro runs the script with the JSR223 engine named by the language parameter.
• GitHub code search of the xwiki organization: no public XWiki Standard page call of the macro was found, only the test resources of its own module.

C1: the name "Content" and the description "The script to execute" are clear for a developer macro.

C2: the content is mandatory, which is right, an empty script does nothing.

C4: a plain text area in the Edit Macro dialog, counted under E6.

C6: the content comes first, before the optional parameters.

C1: the description with its examples is clear for a developer macro. It says "List of JARs" without saying how to separate several values. The name is the ID.

C3: empty means no extra JAR, which is the right default.

C4, minor: a free text field for attachment references or URLs, with no picker, and a missing attachment is reported as a missing script engine, see E2. The values are free text, so the KO is minor.

C6: the field comes first, before the language that the common example sets, but both are visible in the dialog without scrolling, so it is OK.

C8: a rarely used parameter, set by no example of the documentation, and it is not marked as advanced.

C9: the parameter belongs to the script macros and a script in python, groovy or another engine can need a library on its class loader, so it has a realistic use, even with no documented example.

C13: a list of references in a single field with the separator undeclared: "a.jar, b.jar" is refused and the description does not say which separator to use.

C1, minor: the description "The identifier of the script language ("groovy", "python", etc)" gives examples of values, which is OK for a free field, but it does not say that an empty value runs nothing and shows the script as text, and that the identifier is case sensitive, "PYTHON" is refused.

C2: the macro cannot do anything without it: with no language the script is not run and its source is rendered as plain text, see I5. It should be mandatory, so this is a KO.

C3: the field opens empty and no single language is used in most cases, so no value is worth preselecting. Since it should be mandatory, an empty first field is OK.

C4: a free text field for an identifier chosen among the script engines installed on the wiki, a select could offer them, and a wrong value is refused with a message about the engine, see E2.

C5: four fields in the group, content included five, within the limit.

C6: the field is second, after jars, and visible in the dialog without scrolling, so it is OK.

C8: it is the essential parameter of the macro, so it is rightly not advanced.

C9: realistic use, every example of the documentation sets it.

C1: the description "Specifies whether the output result should be inserted back in the page" is understandable for a developer macro. The English name is the ID, "output".

C3: the checkbox preselects the default, true.

C4: a checkbox for a boolean.

C6: no common example sets it, and it is visible in the group with only three other fields.

C8: output="false" is the way to run a script that only sets variables, which is a frequent use, so it is not rarely used. Recorded like output of velocity.

C9: realistic use, the examples of the documentation of the script macros set it.

C1: the description "Specifies whether wiki syntax in the script execution result will be rendered or not" is clear for a developer macro. The English name is the ID, "wiki".

C3: the checkbox preselects the default, true.

C4: a checkbox for a boolean.

C8, minor: wiki="false" is a realistic but rare use, for a script that outputs text with wiki characters, and the field is not marked as advanced. Recorded like wiki of velocity.

C9: realistic use, for a script that outputs text with wiki characters.