Re-factor selection of entity type and bundle in config forms

Hmm not sure whether this should be here or a separate feature request... we're using Easy Email to send various automated mails to users. We've been using views to create a list of recipients, and feeding them into Entity Aware Custom Events, triggering a notification event. This all works great -- however, for each different email template we want to send, we need to create a different custom event which then creates the appropriate email from the easy email template.

Easy Email uses the core entity system, and each template is a new bundle. We could eliminate a lot of extra custom events if we could pass the bundle in as a token.

I like the current ability to select a specific entity type and bundle, but if this is being refactored, it seems like having them split into entity type and bundle fields, with an option to allow the bundle to be specified by a token, would be a nice improvement!

@freelock this is a good place for your suggestion. In summary, I think the challenge is even more complex. In the case of entity type and bundle, there are these use cases:

• With a single drop-down, we have only valid list of value combinations. If we break that up into 2 fields, then the seconds needs to change its list of values dynamically, when the first one changes.
• If we also want to allow tokens, we can't work with drop-downs any longer, unless there is a widget that allows a drop down and optionally a text field?
• If a plugin supports multiple values, not just a single one, that adds a whole layer of extra difficulty.

I think, we need to wait until we support Drupal form API, and then we can think about a form widget that maybe supports all these options. But then the beauty will be that other plugins could also benefit from that.

This is related to ✨ Add "Use token" option to drop-down lists Active