Suggest the sections, templates and UI extensions in the fields of the content reuse macros

The content reuse macros take generated or internal identifiers in plain text fields of the Edit Macro dialog: a heading id, a template file name, a UI extension or an extension point. The user has to know the exact value, and a typo renders nothing or an error.

The macros to change, with the file where most of the fix is done:

• display: DisplayMacroParameters.java.
• include: IncludeMacroParameters.java.
• template: TemplateMacroParameters.java.
• uiextension: UIExtensionMacroParameters.java.
• uiextensions: UIExtensionsMacroParameters.java.

The main problems:

• The section of display and include is the generated id of a heading of the chosen page, like HMyHeading, which the user has to work out: the headings of that page could be offered, so the list depends on the page field.
• The template, UI extension and extension point are identifiers that XWiki knows at runtime, which a searchable list could offer to the developers who use these macros.

Depends on

Most of these fields cannot be offered before these generic changes, each giving the macro the means to declare the expected value:

• XWIKI-23045, which lets a parameter get its values from a provider, with or without custom values.
• XWIKI-25180, which lets a parameter depend on another one, whose value its list of values follows.

KOs covered

Impact found on macro fluidity

These 5 KOs come from the WYSIWYG usability audit of the macros, under the criterion C4 input-assistance of its usability criteria. The page of each macro, linked in the table, has the full notes and the steps to reproduce. Fixing them means changing the declaration of the parameters in the macro definitions.