Opening an issue for this, as a follow up to the following other issues:
Summary: farmOS strives to make it as easy as possible for module developers to extend it. In order to make it easier for modules to add fields, we use Entity API bundle plugins (
#2817751: Create an API for bundle plugins →
) for asset, log, and plan entities with base/bundle field definitions defined in code (
#3183372: Convert config fields to base/bundle fields →
), and we provide a hook for adding fields to existing bundles (
#3188055: Provide a hook for adding bundle fields →
).
Consider whether it is worth it to use bundle plugins for taxonomy terms as well. This is a more invasive change to Drupal core functionality (taxonomy terms), so it may require more testing than our other primary asset types did.
Alternatively, we may decide it's not worth it, and we accept that config fields will be used instead. This poses the same challenges and limitations outlined in #3175497: [META] Allowing optional/contrib modules to add fields to bundles → .
TBD
None.
None.
None.
Closed: won't fix
2.0
Miscellaneous
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I think this would be a breaking change, because it would require all modules that provide a taxonomy vocabulary via config/install/taxonomy.vocabulary.*.yml to *also* provide a bundle plugin class PHP file. If any module does not provide one (eg a contrib module), it would cause an error (I think).
So this may need to wait for farmOS 4.x, if we do it at all.