Skip to content

Add options flow to RainMachine#42241

Merged
bachya merged 2 commits intohome-assistant:devfrom
bachya:rainmachine-options-flow
Oct 28, 2020
Merged

Add options flow to RainMachine#42241
bachya merged 2 commits intohome-assistant:devfrom
bachya:rainmachine-options-flow

Conversation

@bachya
Copy link
Copy Markdown
Contributor

@bachya bachya commented Oct 22, 2020

Proposed change

This PR adds an options flow to RainMachine and adds an appropriate parameter (the default zone runtime) to it.

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

  • This PR fixes or closes issue: N/A
  • This PR is related to issue: N/A
  • Link to documentation pull request: N/A

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:

@bachya bachya force-pushed the rainmachine-options-flow branch from ede6988 to d5973a2 Compare October 25, 2020 19:05
@bachya bachya merged commit e61e8fa into home-assistant:dev Oct 28, 2020
@bachya bachya deleted the rainmachine-options-flow branch October 28, 2020 21:53
]:
hass.services.async_register(DOMAIN, service, method, schema=schema)

config_entry.add_update_listener(async_reload_entry)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We should save the unsubscribe callback returned here and call that on entry unload.

https://developers.home-assistant.io/docs/config_entries_options_flow_handler#signal-updates

with patch(
"homeassistant.components.rainmachine.async_setup_entry", return_value=True
):
result = await hass.config_entries.options.async_init(config_entry.entry_id)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We need to set up the integration before starting the options flow to make sure that the config flow module is loaded. Otherwise we're relying on the other tests to do that.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The config entry is already set up above (lines 14-20); are you thinking something else?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I don't see that. We only create a mock config entry and add it to hass. It needs to be set up with hass.config_entries.async_setup.

@bachya bachya mentioned this pull request Oct 28, 2020
21 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants