Do you know e.g. Tasker for Android?
You just declare a Variable by setting it.
If it is all lowercase, its a temporary, only for this Task/Scope.
If it contains Uppercases, it is permament.
Really, really easy.
Combined with an e.g. Wildcard delete, or sorting for metadata (where is it used) it should be really easy to Maintain.
And i dont speak against helpers! But it is really a brake sometimes and kicks me out if i am in ‘Developing’. And if you have the Need for more Variables, it can take you really Hours.
Fair enough. Probably not. I do it, because i want a function HA doesnt have.
E.g. the 15x5 Queries - it have it only, because there is no built in Option to query Historic States by Templates.
Why do i do this? Because it is, for me, Nonsense to group energy Consumption by Month. I can never tell by looking at it, how the actual Month is going. But this is, what matters to me. So i compare 7/31/365 Days with 7/31/365 Days.
Whatever.
Maybe many Users will never set up a Basic Jinja2 Template. Or give up frustrated. They presumable dont care about Helpers or Vars anyway.
Sure it would make it easier. But why not having Vars that get declared by just setting them, if that would make even those steps unneccesary?
If you forget to maintain Vars, you will forget about maintaining Helpers as well.
Maybe its not a Bug, but a Feature to make it so cumbersome to set Helpers, as you will think about it three times if you need it…
Real Solution? Maybe. Still, you would need to set up helpers. My personal Experience (which should not be a rant at all!), is that many Developers dont see thats Important, or dont have the Time, or abdoned the Project completely, or…
The Real Real Solution would be probably to learn programming, fork and offer Pull Requests for everything But why - if there are examples in Wild life that prove how easy such Things can be solved.
By having global, self-declaring Variables that can be used just everywhere