Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure homekit yaml config works when there is an ignored config entry #48175

Merged
merged 2 commits into from Mar 22, 2021

Conversation

bdraco
Copy link
Member

@bdraco bdraco commented Mar 21, 2021

Proposed change

Ensure homekit yaml config works when there is an ignored config entry

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • The code has been formatted using Black (black --fast homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

  • No score or internal
  • 馃 Silver
  • 馃 Gold
  • 馃弳 Platinum

To help with the load of incoming pull requests:

@project-bot project-bot bot added this to Needs review in Dev Mar 21, 2021
@project-bot project-bot bot moved this from Needs review to By Code Owner in Dev Mar 21, 2021
@@ -222,7 +222,7 @@ def _async_current_names(self):
return {
entry.data[CONF_NAME]
for entry in self._async_current_entries()
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Async current entries ignores the arg to skip ignored if it's not user flow

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since that's fixed, I used it directly

Dev automation moved this from By Code Owner to Reviewer approved Mar 22, 2021
@bdraco
Copy link
Member Author

bdraco commented Mar 22, 2021

I guess I can use the other one that just merged to make this simplier

@bdraco bdraco force-pushed the fix_homekit_with_ignored_entry branch from edc1102 to be0bac8 Compare March 22, 2021 05:21
@bdraco
Copy link
Member Author

bdraco commented Mar 22, 2021

ERROR tests/components/totalconnect/test_config_flow.py::test_reauth[pyloop] unrelated test failure

@bdraco bdraco merged commit 6b93c40 into home-assistant:dev Mar 22, 2021
Dev automation moved this from Reviewer approved to Done Mar 22, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Mar 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Dev
  
Done
Development

Successfully merging this pull request may close these issues.

HomeKit integration via YAML not working
3 participants