I haven’t come very far in my “probing”, but what I have done so far is to add support for specifying more details on the add-on level.
In my development OH installation, this add-on now shows up as this (never mind that “Provisioned With” is blank - it’s because I haven’t actually provided a “resource” yet):
As you can see from the test add-on, I’ve added more information that what is currently displayed, but changes are needed in MainUI to display this. Some of the existing add-on properties doesn’t seem to be in use (as far as I can tell, it’s hard to get a complete overview), like ‘keywords’ and license. I’ve added them anyway, as it can’t hurt if that’s supported by the Marketplace if they gain some use in the future. The “logic” I’ve currently built doesn’t require that any property is specified, it only adds them if they are present.
The idea is that you can optionally specify a new code fenced section using addon as the “language” (instead of yaml, json etc), and if this section exists, the key/value pairs that are found and are valid, are used. That means that it should not break existing add-ons without this information, it’s just a way to specify additional information. I’ve also made it so that this “addon section” is hidden from display when browsing add-ons from the OH Marketplace (it is obviously visible when browsing the forum).
There are loads and loads of things I’ve been thinking of that isn’t here yet - but I’d like so feedback to the approach/idea itself. Do you think this is a “viable way” of specifying this additional information?