Ensure we always show backend error in automation and script editor#8139
Merged
spacegaier merged 3 commits intohome-assistant:devfrom Jan 13, 2021
Merged
Conversation
bramkragten
reviewed
Jan 13, 2021
Co-authored-by: Bram Kragten <mail@bramkragten.nl>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Breaking change
Proposed change
I have an automation currently that I cannot save due to some backend failöure (separate issue). However, in that case the frontend only shows an empty toast as the backend is not actually providing a proper error message.
This PR ensures that we at least show the more generic error to inform the user.
Debug screenshot of generic backend response:

Type of change
Example configuration
Additional information
Checklist
If user exposed functionality or configuration variables are added/changed: