Add jinja2 editor to template triggers/conditions

[frenck]

Proposed change

Add the code editor with Jinja2 syntax to the template trigger and template condition.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[zsarnett]

This shouldn't be needed

[frenck]

It is :)

Trigger event changed assume FormElement (from mwc-base, which our code editor isn't).
This we need to supply the bare minimum we depend upon, which is the name (used by the handleChangeEvent in the ha-automation-trigger-row.ts file.

[zsarnett]

You can have the name on the element in ha-automation-trigger-row.ts without needing to add the property in the element. It will still set the name attribute and should be gettable

[frenck]

Ok, so I'm a noob at frontend stuff and you would need to help / provide a hint me on this one.

It tried setting the name on HTML, but apparently: that is not enough to access it as a property. So, I guess I'm missing something?

[zsarnett]

Use can use .name=${"name"}

This will set it as a property. You are correct that it needs the Attr when setting it with just name=""