Add selectors to ha-form

[balloob]

Breaking change

Proposed change

Add support for selectors in ha-form.

Goal is to eventually remove all other types and be selector only.

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

[bramkragten]

We should decided which one to use by default, maybe drop 1 from the type

[bramkragten]

I would say required

[balloob]

Sure, but let's do that in a future PR. We will need to check what is used where.

For the backend, both required and optional fields can have a default, which is filled in when key is omitted. So not so required or optional…

[balloob]

I agree with keeping required. Let's update it in another PR. It means rewriting all checks for optional to be !required.

[balloob]

#11538

[balloob]

Don't understand why the error would happen

[balloob]

I bet this has something to do with icons being imported by the supervisor now that we import ha-selector. I bet @bramkragten knows the answer when he wakes up

[bramkragten]

Yep, that's the issue

[balloob]

selector-entity -> ha-entity-picker -> state-badge -> ha-state-icon -> ha-icon -> 💣

[balloob]

I've fixed it now by blocking ha-icon from being loaded on supervisor builds. It wasn't used since it broke the build. Not sure if this is ok or we should find a solution where we break up selector in a "without icon" version safe for the supervisor and a "with icon" version for HA?

[frenck]

Forgive me for my ignorance/lack of knowledge on this part.

Can't we handle the selector options?
As in, would be nice if multiline was not defined by the schema name.

The same issue also returns in, for example, the entity selector. Would be nice if we could pass in data from the flow limiting, e.g., the domain you could select.

[bramkragten]

That is the case, the name is just for the demo. These are the same selectors that are used in blueprints and service calls.

[bramkragten]

I think this is ok. ha-icon should never be used in hassio. Only downside is that we no longer have an indication that there is a ha-icon in the build.