> My understanding is that this issue may occur only for some macros, more specifically for the ones for which the mandatory parameters cannot be marked as such because it's a group of parameters of which one is mandatory but no single one is mandatory, is this correct, Charpentier Lucas (and/or Ilie Andriuta) ?
Yup, that's also what I understand from this situation.
> In this case, isn't this a duplicate of XWIKI-20945 ?
XWIKI-20945 and XWIKI-20944 are both very close to what's described here, but they talk about specific macros. IMO if we provide a proper generic fix for this ticket, XWIKI-20945 and XWIKI-20944 should be `Solved By` it and closed
> Or, if this is for the generic possibility to mark a group of parameters as mandatory, it's the same as XWIKI-23043 ?
AFAIU, this possibility to mark a group of parameters as mandatory is implemented ( XCOMMONS-2738 ) and already somewhat useful since Simon Urli implemented validation based on it for XWIKI-23043. But validation is not the only thing we want to do with these new marks, one thing is to (like "standard" mandatory fields) to open the edition dialog when creating a macro that contains at least one field with a "mandatory feature" mark. Having the mandatory feature mark influence the creation UX as expected would fix the problem described in this ticket. Note that back in March I assumed I'd have to implement what was done in XWIKI-23043 just so that this feature would make sense
___ Sidenote: I did forget about this ticket for a few releases, unassigning myself. If we don't need to solve it quickly, I'll try to handle it into the September roadmap.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.