Conversation
|
The base class methods are here: core/homeassistant/config_entries.py Lines 1353 to 1357 in 363de37 core/homeassistant/config_entries.py Lines 1359 to 1363 in 363de37 core/homeassistant/config_entries.py Lines 1365 to 1369 in 363de37 core/homeassistant/config_entries.py Lines 1371 to 1375 in 363de37 core/homeassistant/config_entries.py Lines 1377 to 1381 in 363de37 |
|
Is this a breaking change for custom components? |
|
|
||
| return await self.async_step_confirm() | ||
|
|
||
| async_step_zeroconf = async_step_discovery |
There was a problem hiding this comment.
These need to be here because async_step_discovery logic needs to be assigned to all these discovery steps. It's not assigning the same thing.
There was a problem hiding this comment.
@balloob I have marked this as draft for now.
It was linked to PR 59503 - maybe you can take a look at this comment?
#59503 (comment)
|
I am closing this following the discussions on #59503 (comment) |
Proposed change
Cleanup DiscoveryFlowHandler method redefinitions (
async_step_zeroconf,async_step_ssdp,async_step_mqtt,async_step_homekit,async_step_dhcp) which seem redundant with the inherited definitions inConfigFlow.These redefinitions are causing mypy inheritance issues when working on #59503.
See the failed run https://github.com/home-assistant/core/runs/4167772127?check_suite_focus=true#step:7:12
Also see home-assistant/architecture#663
Type of change
Additional information
Checklist
black --fast homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all..coveragerc.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: