Now that a concept of a plugin manager is included, plugins can be explicitly defined in classes. This is good, but limited in scalability. We should have a plugin derivative mechanism similar to what Drupal core provides where a plugin deriver exists which contains logic for defining a collection of plugins from a single "deriver class".
An example use case of this would be having template plugins dynamically discovered based on set configuration values that configure source, destination, tokens available, etc... which would allow us to reduce the (as of now) 9 different templates defined explicitly in template classes to a single template.
Now that a concept of a plugin manager is included, plugins can be explicitly defined in classes. This is good, but limited in scalability. We should have a plugin derivative mechanism similar to what Drupal core provides where a plugin deriver exists which contains logic for defining a collection of plugins from a single "deriver class".
An example use case of this would be having template plugins dynamically discovered based on set configuration values that configure source, destination, tokens available, etc... which would allow us to reduce the (as of now) 9 different templates defined explicitly in template classes to a single template.