Javier Peletier

@ssieb yes, it would conflict. It is an important discussion, because we have different options I think: ## Option 1. Do nothing (breaking change) Users of `homeassistant.service` action would have...

> I like the use of YAML tags for the `!if` and `!for` statements in this PR! Thank you @jpeletier for driving this effort forward, I really like the approach...

> Just a wild idea, but maybe `${}` AND `${{ }}` (where the former only allows vars, and latter is for full jinja2 expressions) Why would we restrict `${}` to...

@OttoWinter This should be ready for review. Here are the changes: * Universal syntax `${ expression }` does jinja and substitutions and is backward-compatible. * Substitutions may contain values other...

@bearpawmaxim This PR does not provide item overriding, but it is true that you could achieve similar functionality. Let's look at some examples coming from [#3555](https://github.com/esphome/esphome/pull/3555) and how would them...

@quentinmit my last solution is ugly AF, just hacking around trying to answer the question from @bearpawmaxim :-)

@OttoWinter Any further comments on this PR. We'd really like to see this merged. Thanks

Hi @jimtng I reached the conclusion with @quentinmit that `!extend` would be more convenient to extend packages that you didn't write. However, if you are the package author, this PR...

@OttoWinter @jesserockz please consider this PR which would greatly simplify configs, there is a lot of work behind it. Thanks

@fxstein @jacauc I will fix conflicts and update this PR if I see approvals from @OttoWinter @jesserockz. This would indeed simplify complex configs, or remove the need for scripts that...