Letting custom entities use new more-info design #17790
Unanswered
redstone99
asked this question in
Dashboard
Replies: 1 comment
-
I created a PR implementing option 1: #17793 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
It'd be nice if custom entity types could use the new more-info design so as to have more control over how entity information is displayed. At present, the default more-info card starts with history and logbook sections, followed after by a custom more-info section if the
custom_ui_more_info
attribute is defined on the entity. For some entity types, the history & logbook sections aren't useful. I can see two alternative ways of improving this.custom_ui_new_more_info
attribute that, when specified, directs the front-end to use the new design. This is probably the simplest solution.or
custom_ui_more_info
,custom_ui_state_card
andicon
. These are all specified per-entity, presumably increasing the size of data that the frontend has to load. Registering behavior per-entity-type rather than per-entity would presumably lower the data size, which probably is a good thing.Thoughts?
Josh
Beta Was this translation helpful? Give feedback.
All reactions