Paulus Schoutsen
Paulus Schoutsen
Well step 1 is to make sure that we can correctly traverse contexts between executor and async land.
So we can have `hass`, `request` and `context` vars, that would be awesome, especially for things like voluptuous validation.
Yes, but Penny showed how it could work here: https://github.com/home-assistant/architecture/issues/181#issuecomment-475907865
I don't believe in using GitHub issues. They are too limited. Especially if we would want such a system to be hooked into Home Assistant. Because if we can organize...
let's move these discussions to the alerts repo.
@DubhAd do you think the new alerts website will be a sufficient fix for this issue?
No implementations yet but I wrote them down. 1. https://github.com/home-assistant/alerts.home-assistant.io/issues/7 2. https://github.com/home-assistant/alerts.home-assistant.io/issues/8
I think that we can solve this using the UI and existing infrastructure. - Allow rendering async_abort as being a successful abort. - Whenever a discovered config flow has the...
I think that we should require a unique ID for updating a config entry. How else will we be able to refer to it? I've added `step_id` to the flows...
Very good point 😆