I now just took the existing code and put a menu item in front of it.
I didn’t mean this as blocking either but couldn’t help mentioning :)
How about moving the gist of the message to the beginning of the phrase?
From:
To catch and prevent most of these errors, it is recommended to build your extension using the…
My test file: __MACOSX_missing_wheel.zip
Final notes (which some of it was from 4.1 already, but some are new). I find the order of the menus a bit strange. It is neither…
We can also remove "rigify" from scripts/addons_core/bl_pkg/extensions_map_from_legacy_addons.py +81.
All in all it seems good. I'm building the branch now to test it.
Shouldn't this be blender: (4, 2, 0)? I thought that the recent changes Nathan did were specific to the 4.2.0 API.
This is not a bug, but indeed more a known issue. The behaviour in 4.2/4.3, although not ideal, copies what we did for add-ons before.
This case here is not the add-on name but its internal "module" name. This is a corner case that happens if users deliberately removed an add-on from the installation folder. In this case we don't…
The changes seem to be suggesting extensions names, taglines and (add-on) module names to be translatable. Which are not.
tag-lines are not translated, why to use iface_() here?