plugins.json doesn't include the truth. E.g. in the screenshot above my DLP-Plugin is listed, because the plugin-repository information is not up to date. But the DLP-plugin works with python 3 and OP1.4.
IMHO: We need to improve the content of the
plugins.json and not an additional plugin (don't get me wrong, the "Python3PluginCompatibilityCheck-Plugin" is helpful, but it is just a workaround)
Why not executing a shell-, nodejs-, python- or ruby-script to crawl the compatibility-information, before executing Jekyll.
- python grapCompatibility.py
- bundle exec jekyll build
The script look into each single plugin-repository, parse the
__init__.py file for compatibility-information (beside python, just add the other stuff, like OP-, OS-Version) and build the
plugin.json file with that information.
Just add some default behaviour, if not all compatibility-information could be selected. Just grab the info from the plugin-markdown (but add a hint about the source of the information).
In the future the markdown compatibility-information should be deprecated.
Is this to complicated or did I missed something? (For 60request/h limit, we need to switch to auth-user, then we have 5000request/h) see https://developer.github.com/v3/#rate-limiting
What do you think?