You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The README exposes a simple example on how to use auto-entities to create a grid with standalone entity cards, which is an awesome starter point.
However, if you want to use different cards, you're stuck to anything that can receive the entity: prop. The only way to use, for instance, a decluttering-card template is to use the double-auto-entities hack where one of the filters is a template that returns a dict with the details you need for the card...... Which is (1) ugly AF, (2) terrible to write and debug, (3) very confusing and (4) not performant at all.
any chance this idea could be jinja-templated? This would effectively allow people to do their own replacement rules, killing off the dreaded FR: bulk rename option #166
another option is try to follow what was done in custom-ui, which allows us to write basic JS to achieve some value manipulation
The text was updated successfully, but these errors were encountered:
The README exposes a simple example on how to use
auto-entities
to create a grid with standaloneentity
cards, which is an awesome starter point.However, if you want to use different cards, you're stuck to anything that can receive the
entity:
prop. The only way to use, for instance, adecluttering-card
template is to use the double-auto-entities hack where one of the filters is a template that returns a dict with the details you need for the card...... Which is (1) ugly AF, (2) terrible to write and debug, (3) very confusing and (4) not performant at all.A suggestion would be to do it like this:
Bonus points:
custom-ui
, which allows us to write basic JS to achieve some value manipulationThe text was updated successfully, but these errors were encountered: