Context
In the equipment command list, the "action" and "info" type inputs are currently displayed without any color differentiation, making it harder to scan commands at a glance, especially on equipment with many commands.
These colors are already applied in the equipment's advanced configuration window, where the same types are displayed as badges (var(--al-warning-color) for action, var(--al-primary-color) for info).
This was originally raised on the community forum: https://community.jeedom.com/t/evolution-couleur-par-defaut-pour-les-boutons-action-et-info-des-equipements/149571
Note: depending on the plugin, some type fields may render as select elements instead of disabled inputs. This edge case may need to be accounted for in the implementation, though it is debatable whether a command type should be editable at all once defined.
Goal
Improve readability of the command list by applying consistent colors across views, without requiring manual CSS customization from the user.
Consideration
If some users might prefer the current neutral appearance, a configuration option could be worth discussing.
Context
In the equipment command list, the "action" and "info" type inputs are currently displayed without any color differentiation, making it harder to scan commands at a glance, especially on equipment with many commands.
These colors are already applied in the equipment's advanced configuration window, where the same types are displayed as badges (
var(--al-warning-color)for action,var(--al-primary-color)for info).This was originally raised on the community forum: https://community.jeedom.com/t/evolution-couleur-par-defaut-pour-les-boutons-action-et-info-des-equipements/149571
Note: depending on the plugin, some type fields may render as select elements instead of disabled inputs. This edge case may need to be accounted for in the implementation, though it is debatable whether a command type should be editable at all once defined.
Goal
Improve readability of the command list by applying consistent colors across views, without requiring manual CSS customization from the user.
Consideration
If some users might prefer the current neutral appearance, a configuration option could be worth discussing.