Skip to content

Use single_instance_allowed for webhook config flows#40965

Merged
MartinHjelmare merged 1 commit intohome-assistant:devfrom
springstan:use-single-instance-allowed-base-string-for-webhook-config-flows
Oct 1, 2020
Merged

Use single_instance_allowed for webhook config flows#40965
MartinHjelmare merged 1 commit intohome-assistant:devfrom
springstan:use-single-instance-allowed-base-string-for-webhook-config-flows

Conversation

@springstan
Copy link
Copy Markdown
Member

Breaking change

Proposed change

Following the suggestion in #40959 (comment)

Webhook config flows previously used the base string one_instance_allowed this has now been replaced by single_instance_allowed to be consistent with non-webook config flows.

cc @ludeeus

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:

Copy link
Copy Markdown
Member

@MartinHjelmare MartinHjelmare left a comment

Choose a reason for hiding this comment

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

Please finish one integration per PR instead so we can keep track of what integrations are done.

@springstan
Copy link
Copy Markdown
Member Author

I can see where you are coming from but once it has been changed homeassistant/helpers/config_entry_flow.py it has to be changed in all webhook config flows. So IMHO it should be done in one PR instead of multiple PRs. Still I am open to creating multiple PRs if that is much better for transparency during Hacktober.

Copy link
Copy Markdown
Member

@MartinHjelmare MartinHjelmare left a comment

Choose a reason for hiding this comment

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

Thanks!

"""Handle a user initiated set up flow to create a webhook."""
if not self._allow_multiple and self._async_current_entries():
return self.async_abort(reason="one_instance_allowed")
return self.async_abort(reason="single_instance_allowed")
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 didn't see that you're changing this string. Then it's ok to do all integrations in one PR for this string.

@MartinHjelmare MartinHjelmare merged commit c7ebfdb into home-assistant:dev Oct 1, 2020
@springstan springstan deleted the use-single-instance-allowed-base-string-for-webhook-config-flows branch October 1, 2020 20:44
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