allow card_param to be a path

[mrnerdhair]

This parses card_param as a path to a property rather than the name of a property which must be on an immediate child. This is useful if you'd like to use a wrapper card rather than a card which shows entities directly.

[ildar170975]

@mrnerdhair
Could you post an example where this feature can be used?
I guess you mean this case:

type: some_card
...
some_option:
  ...
  option_to_be_populated:
    - ...
    - ...
...

and then you can use

card_param: some_option.option_to_be_populated

But I do not recall a card with such structure.

[mrnerdhair]

I was trying to do something along the lines of this, where card.entities was the correct path:

type: custom:mod-card
card:
  type: vertical-stack
  entities: []
card_mod:
  style: |
    ha-card {
      // ...
    }

[ildar170975]

Well, mod-card could be a good example - but:
mod-card is needed for cards w/o ha-card - and vertical-stack is a good example, but it does not have an entities option. Perhaps you should have meant a cards option:

type: custom:auto-entities
card_param: card.cards
card:
  type: custom:mod-card
  card:
    type: vertical-stack
  card_mod: ...
filter:
  include:
    - domain: person
      options:
        type: entity

Do you know any other possible applications apart of mod-card?