code

• Code macro translations, oldcore ApplicationResources.properties: the English names of the parameters are set to their IDs, like rendering.macro.code.parameter.language.name=language, while French and German mostly translate them.
• CodeMacroParameters.java: extends BoxMacroParameters, so cssClass, image, title and width come from the box macro; source is marked as advanced.

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

C1: "A CSS class to add to the box element" uses technical terms, which fit a styling parameter: describing it another way would only be more confusing.

C5, minor: the 8 fields, content included, are all in the single group "Optional parameters", above 7. The same holds for every parameter.

C8: a styling parameter that is rarely used, and no common example sets it, but it is not marked as advanced.

C1: the description "the image which is to be displayed in the message box" calls the code block a message box, and does not say what value is expected, an attachment or a URL.

C4: a free text field, with no image picker, although the type is a resource reference; a reference to a missing attachment is accepted.

C9: inherited from box, and no example sets it: users do not expect an image on a code block, so the field is only noise in the dialog and should be hidden for this macro.

C1, minor: the description "the language identifier (java, python, etc.)" does not say that an empty value detects the language automatically, which is what the empty field means, nor that "none" turns the highlighting off.

C4: a free text field, although the accepted values are the fixed list of Pygments languages: the user has to know the identifier, like "html" or "bash", and a wrong one, like "nosuchlanguage", is accepted silently. A select with suggestions could be used.

C6: language is the only parameter set in the most common example, but it comes fourth, after Content, CssClass and Image, in alphabetical order.

C3: the select preselects Plain, the declared default.

C4: a free text field for a typed reference, like "page:Page/SubPage" or "attachment:[email protected]", with no page or attachment picker: the user has to know the syntax of the reference. A proper field needs design work, since some types, like "script:", cannot have a picker.

C7: source and the content are alternative ways to give the code, the source replacing the content, but the Edit Macro dialog cannot present them as one choice, since only parameters can be part of a feature. A limitation of the macro system, listed in the Cross-macro findings, reported as XWIKI-25456.

C9: advanced, and used by realistic examples of the documentation, like highlighting an attachment.

C1: the description "the title which is to be displayed in the message box" calls the code block a message box. It does not say either that the title accepts wiki syntax.

C9: no example sets it, but a file name above a snippet is a realistic use.

C13: only accepts a CSS length "in px or %", but declares no format: "abc" is accepted by the dialog and output as style="width:abc".