-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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
Extract lovelace to it's own component #16816
Conversation
) | ||
except FileNotFoundError: | ||
error = ('file_not_found', | ||
'Could not find ui-lovelace.yaml in your config dir.') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
continuation line over-indented for visual indent
"""Send lovelace UI config over websocket config.""" | ||
error = None | ||
try: | ||
config = await hass.async_add_job( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use async_add_executor_job
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤦♂️
Description:
This moves Lovelace from frontend component to it's own. Changes websocket command but made backwards compatible to avoid frontend update issues.
Example entry for
configuration.yaml
(if applicable):frontend:
Checklist:
tox
. Your PR cannot be merged unless tests passIf the code does not interact with devices: