Support for modules to operate on the card's configuration

[Airblader]

OK, this is a pretty advanced feature for modules, but I think there are many either new use cases requiring this, or existing use cases that would just get easier by having this.

What if modules could actually operate on the card's configuration object, rather than just reading it?

Disclaimer...

I have played around with whether this is already possible, but I don't believe it is, even if trying to be "hacky".

This would give modules the ability to mutate existing state as needed (e.g. the get_state_attribute module requires "Show attribute" to be set, but it could just force this itself), or even create state. Want to add the same complex set of sub-buttons to several cards? Just write a module that adds them!

In a sense, this is like a super-charged way of templating Bubble Cards, because modules can be much more context-sensitive than templates.

I have no idea if this is architecturally even feasible at all, but one can dream, so here I am. 🙂

[Airblader]

Things like #2097 would also become possible with this, I think.

[Clooos]

Haha, this is the next big feature I had in mind, what I want to achieve is to also give the possibility to save card templates directly in the editor, then the hability to reuse or even share these with variables to fill if the user want to push a template further.

This feature will need a lot of work and I'm maybe not ready to work on this just yet, v3.1.0 was already a challenge by adding way too many new options in only one release (without adding real breaking changes).

But I could check how to implement a clean way to mutate the config directly from a module, this part would be more doable 👌

[Airblader]

That would be fantastic, and could serve to some extent as a way to validate the idea!