Skip to content

Use common strings in traccar config flow#40959

Closed
springstan wants to merge 1 commit intohome-assistant:devfrom
springstan:use-common-strings-for-traccar-config-flow#
Closed

Use common strings in traccar config flow#40959
springstan wants to merge 1 commit intohome-assistant:devfrom
springstan:use-common-strings-for-traccar-config-flow#

Conversation

@springstan
Copy link
Copy Markdown
Member

Breaking change

Proposed change

Use common strings in traccar config flow as described in #40578

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:

},
"abort": {
"one_instance_allowed": "Only a single instance is necessary.",
"single_instance_allowed": "[%key:common::config_flow::abort::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.

For webhook flows the key needs to be one_instance_allowed

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Oh okay did not know that, will close this PR and open another one to add this string to the base strings.

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.

Probably better to change the Base class for webhook flows to use the same as others ;)

Consistency 🎉

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

That is an even better idea 😄
I am a big fan of consistency as well 🎊

@springstan springstan closed this Oct 1, 2020
@springstan springstan deleted the use-common-strings-for-traccar-config-flow# branch October 1, 2020 12:02
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.

4 participants