Getting a quick look at the topic, what I'd imagine as a perfect solution would be that we add a "conflict" and a "shorthand" sections in the macro listing. The conflict section would show what macro names collide, and allow to select which one is winning (but it probably goes against the component logic... not sure it'd make sense to allow this). The shorthand section would allow users to define alternative names for some macros, this is a way that would allow using both macros at the same time (but could create even more collisions...). How we handle hidden macros with all these would create a whole lot of edge cases...
Pretty sure we don't want to get into a complex system for a user need that seems quite limited.
In any case, I think we can close this issue as won't fix and possibly redirect to an issue corresponding to the idea I've described (we possibly already have such as a jira but couldn't find it ATM).
I asked CC and it couldn't find any ticket about this. Created PAGELOGS-2 .
+1 to close this one as a won't fix.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
