I think mentions to categories and tags should be excluded from this warning, and maybe all internal topic references as well (i.e suppress this warning for all links going to the forum you’re at).
Thank you for creating this topic. I am slightly annoyed by this warning, too. I don’t see a warning for using bug in my reply, so this seems to be limited to category mentions. I don’t remember when this started, but I just tried, and it doesn’t happen on a forum that is still on v3.6.0.beta1-dev.
I am not sure I agree with that. I usually find it quite helpful when I am told that a theme component has already been linked in a topic. Sometimes I miss that something had already been suggested.
Aside: I tried to make a category mention with #bug but apparently this became a tag mention. I’m not sure if it’s desirable to have a tag with the same name as a category.
I think that’s because #contribute:bug is a subcategory now. There are lots of duplicates, and I don’t think it was a problem before.
I think usually the category is offered first, because it’s an exact match, for example for #documentationDocumentation results in the category not in #documentation::tagdocumentation and is offered first in the autocomplete:
For #bugbug it’s the other way around. This is now matched to the tag instead of the subcategory (one aspect of making everything subcategories I do not enjoy)
I think sometimes what is offered also depends on the context in a topic Contribute > Lounge is offered before the chat channel with the same name. But in chat the channel is offered first
the tag can be used in private subcategories, so there’s some potential use for it outside of the public bug category… but it’s not used much so maybe it’s worth cleaning up and abandoning the tag