8000 Add zwave_js options flow to reconfigure server by MartinHjelmare · Pull Request #51840 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add zwave_js options flow to reconfigure server #51840

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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 24, 2021

Conversation

MartinHjelmare
Copy link
Member
@MartinHjelmare MartinHjelmare commented Jun 14, 2021

Breaking change

Proposed change

  • Add options flow to reconfigure server settings, including add-on if used.
  • Add restart add-on support in add-on manager. Restarting the add-on is needed to apply changed add-on settings.
  • Expose all add-on options in the options flow:
    • device
    • network key
    • log level
    • emulate hardware

TODO

  • Investigate missing progress step dialog text in options flow.

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

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:

@probot-home-assistant
Copy link

Hey there @home-assistant/z-wave, mind taking a look at this pull request as its been labeled with an integration (zwave_js) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

@MartinHjelmare MartinHjelmare marked this pull request as draft June 14, 2021 12:27
@MartinHjelmare MartinHjelmare marked this pull request as ready for review June 15, 2021 10:02
@balloob balloob requested a review from emontnemery June 21, 2021 17:11
Copy link
Contributor
@emontnemery emontnemery left a comment

Choose a reason for hiding this comment

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

LGTM

Comment on lines +1175 to +1181
{"device": "/test", "network_key": "abc123"},
{
"usb_path": "/new",
"network_key": "new123",
"log_level": "info",
"emulate_hardware": False,
},
Copy link
Contributor

Choose a reason for hiding this comment

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

Just a side note:
old_addon_options and new_addon_options are same in both parametrizations, but it's nice for clarity to specify them here.
Is there some nice pattern to avoid duplicating them though?

Copy link
Member Author
@MartinHjelmare MartinHjelmare Jun 22, 2021

Choose a reason for hiding this comment

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

We could store them in two constants. For most of these tests it's mostly needed to see that the old is different from the new options, not exactly what the difference is. There are some exceptions where the details are interesting.

@MartinHjelmare MartinHjelmare merged commit 0e5040d into dev Jun 24, 2021
@MartinHjelmare MartinHjelmare deleted the add-zwave_js-flow-options branch June 24, 2021 11:15
@github-actions github-actions bot locked and limited conversation to collaborators Jun 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0