Improve authentication error handling in config flow #246
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.
Before this PR, entering an incorrect username or password in the config flow would cause the form to display “Unexpected error”, while the hass logs would print “Unexpected exception” and a stack trace:
The last line above might also be:
After this PR, nothing is printed in the hass logs (at least not with my default log level), and the user interface displays a seemingly hass-standard “Invalid authentication” message:
The reason why I was messing with that is that I was testing my code changes in another PR, #245.