component-dash shouldn't create multiple cards

[shans]

At the moment, component-dash has to create multiple cards internally, because the configuration file is confined to a simple list of dashboards and globally named configurations. This means that there's no convenient way to request a list of component-dashes with different configurations.

However, multiple internal cards don't flex wrap properly, and there's no convenient way to break the component isolation barrier to make this work.

If we let the dashboard list take a function syntax instead, e.g.

"dashes": [
    "cz-component-dash(Blink>Animation)",
    "cz-component-dash(Internals>Compositing>Animation)",
    ...
]

Then the component dash can be given its name as part of its construction, and use it to index appropriately into the configuration. Later we can even make a lot of this automatic if we want.

[dstoc]

Seems a bit magical -- syntax will get complex when there's more than one string argument. Maybe just:

"dashes": [
    {"name": "cz-component-dash", "config": "Blink>Animation"},
    {"name": "cz-component-dash", "config": "Internals>Compositing>Animation"}
]

[shans]

That could work too. I'd probably call it "key" rather than "config".

The function approach is fine, though - I don't think we'd ever extend it beyond a single string which was nominally intended as a key into a config somewhere.

We could always just support both :P

[dstoc]

Fixed?