In preparation for the central repository migration, we need a system to add categories ("tags") to plugins such that they can be filterable within future built-in plugin downloaders, and possibly within the plugins page itself. While the possible categories can be custom, this would become a problem in the future since plugins may use overlapping but not identical categories. As such, I think that the possible categories should be hardcoded within this Gradle plugin and within the Aliucord core itself.
The list of possible categories would have to be always backwards compatible, and as such should be carefully thought out. I've made a draft of possible categories we can support: (cc @Ushie)
- Theming: Themer, NoUppercase, other color/font/(themed) layout modifying plugins
- Layout: LayoutController, plugins that change or remove layout components in a static way
- Chat: MessageLogger, chat utilities,
- Backport: backports of new functionality from RNA
- Fun: Random niche commands, etc.
In preparation for the central repository migration, we need a system to add categories ("tags") to plugins such that they can be filterable within future built-in plugin downloaders, and possibly within the plugins page itself. While the possible categories can be custom, this would become a problem in the future since plugins may use overlapping but not identical categories. As such, I think that the possible categories should be hardcoded within this Gradle plugin and within the Aliucord core itself.
The list of possible categories would have to be always backwards compatible, and as such should be carefully thought out. I've made a draft of possible categories we can support: (cc @Ushie)