This repository has been archived by the owner on Oct 4, 2019. It is now read-only.
Lovelace card configuration gets scrambled/reordered #248
Comments
@balloob commented on Jan 28, 2019, 1:08 AM UTC: The cause is simple, we don't store the config in yaml format but in json. The solution is not simple (I know of none) |
ghost
mentioned this issue
Mar 9, 2019
@iantrich commented on Mar 9, 2019, 9:08 PM UTC: Going to move this to ui-schema as this is not really a bug, but a preference |
I really hope something can be done about this. Once you start adding multiple stacks, it becomes absolutely horrendous to edit because of this problem. |
ghost
mentioned this issue
Oct 4, 2019
This issue was moved by iantrich to home-assistant/home-assistant-polymer#3913. |
ghost
closed this as completed
Oct 4, 2019
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
move[bot] commented on Jan 28, 2019, 12:54 AM UTC:
rs443 commented on Jan 26, 2019, 8:03 AM UTC:
Home Assistant release with the issue:
0.86
Last working Home Assistant release (if known):
N/A
Operating environment (Hass.io/Docker/Windows/etc.):
Home Assistant on Windows 10, Python 3.6.8
Component/platform:
Lovelace UI
Description of problem:
I started using lovelace in the gui in the 0.86 release. I noticed a cosmetic "issue". When editing a card the lines in the configuration is scrambled. . The configuration is still valid but the lines has switched places. Possibly reordered alphabetically.
This makes is hard to edit a card in the editor, sometimes impossible.
This is an easy example of a card that was created and is readable and easy to understand:
When editing the same card this is the result:
Here is a more complex card that was once readable:
Now its a nightmare to edit:
It is possible to save the configuration without reordering the values?
This issue was moved by cgarwood from home-assistant/home-assistant#20450.
This issue was moved by iantrich from home-assistant/home-assistant-polymer#2601.
The text was updated successfully, but these errors were encountered: