Skip to content

Use reference strings in upnp#41327

Merged
springstan merged 4 commits intohome-assistant:devfrom
SNoof85:patch-15
Oct 6, 2020
Merged

Use reference strings in upnp#41327
springstan merged 4 commits intohome-assistant:devfrom
SNoof85:patch-15

Conversation

@SNoof85
Copy link
Copy Markdown
Contributor

@SNoof85 SNoof85 commented Oct 6, 2020

Breaking change

Proposed change

Use reference strings in upnp

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:

@probot-home-assistant
Copy link
Copy Markdown

Hey there @StevenLooman, mind taking a look at this pull request as its been labeled with an integration (upnp) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

Copy link
Copy Markdown
Member

@balloob balloob left a comment

Choose a reason for hiding this comment

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

🕺

"abort": {
"already_configured": "UPnP/IGD is already configured",
"already_configured": "[%key:common::config_flow::abort::already_configured_service%]",
"no_devices_discovered": "No UPnP/IGDs discovered",
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.

Does this need a reference applied too?

Copy link
Copy Markdown
Contributor Author

@SNoof85 SNoof85 Oct 6, 2020

Choose a reason for hiding this comment

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

Yes we can ;)

Edit : but once again no_devices_found ? It's not same error message and i can't find a corresponding common string for no discovered devices.
But basically it is quite the same error message we could remove no_devices_discoveredand use no_devices_foundin config flow for both cases.

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 think using no_devices_found in both cases makes sense.

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.

let's go for it then

Comment thread homeassistant/components/upnp/strings.json Outdated
Co-authored-by: scheric <38077357+scheric@users.noreply.github.com>
Copy link
Copy Markdown
Member

@springstan springstan left a comment

Choose a reason for hiding this comment

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

Looks good 👍

@springstan springstan merged commit f256d0a into home-assistant:dev Oct 6, 2020
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.

5 participants