-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lovelace card configuration gets scrambled/reordered #2601
Comments
@cgarwood commented on Jan 28, 2019, 12:54 AM UTC: Moving this to the frontend repo so it can get more visibility /move to home-assistant-polymer |
ghost
mentioned this issue
Jan 28, 2019
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) |
Going to move this to ui-schema as this is not really a bug, but a preference |
ghost
mentioned this issue
Mar 9, 2019
ghost
deleted a comment from
iantrich
Mar 9, 2019
This issue was moved by iantrich to home-assistant/ui-schema#248. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@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.
The text was updated successfully, but these errors were encountered: