Allow split component definitions in packages

[thomasloven]

Description:

Two different configuration styles are described in
https://www.home-assistant.io/docs/configuration/devices/#style-2-list-each-device-separately

But only one is allowed in packages according to
https://www.home-assistant.io/docs/configuration/packages/

This change allows "Style 2" configuration in packages.

Related issue: N/A

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.io#6075

Example entry for configuration.yaml (if applicable):

homeassistant:
  packages: !include dir_named packages

packages/my_package.yaml

sensor first:
  - platform: template
    sensors:
      my_sensor_1:
        value_template: 1

sensor second:
  - platform: template
    sensors:
      my_sensor_2:
        value_template: 2

Checklist:

• The code change is tested and works locally.

• Local tests pass with tox. Your PR cannot be merged unless tests pass
  If user exposed functionality or configuration variables are added/changed:

  • Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

• New dependencies have been added to the REQUIREMENTS variable (example).
• New dependencies are only imported inside functions that use them (example).
• New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[homeassistant]

Hi @thomasloven,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[houndci-bot]

line too long (81 > 79 characters)

[homeassistant]

Hi @thomasloven,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[amelchio]

I have looked at this PR before but not commented because I could not believe that such a simple change could work. It was actually less typing to make it work than it was to describe that it did not work.

This area of the code is unknown to me but now I looked at the PR more closely and I don't see why it wouldn't work. That is awesome.

I only have a few suggestions for the comments and you can feel free to ignore those since comment style is subjective anyway.

However, some tests should be added (to tests/test_config.py). I think we will want a test with several entries for the same component being merged in (like light 1:, light 2:) since that was one situation I was wondering about.

[thomasloven]

Thanks. I agree, it's suspiciously simple.

I'll look at implementing a test of some sort too. Thanks for the pointer on where to start!

[thomasloven]

I've added a test that checks that components like light 1: and light 2: are added to the configuration. Making sure they are read correctly, and that the actual configurations are merged is the responsibility of async_process_component_config and not related to my changes.

[balloob]

Congrats on your first PR merged 🎉

[thomasloven]

Thank you!