Skip to content

Move ZHA config panel section translations to the backend#49816

Merged
balloob merged 3 commits intohome-assistant:devfrom
dmulcahey:dm/zha-config-translations-backend
Apr 30, 2021
Merged

Move ZHA config panel section translations to the backend#49816
balloob merged 3 commits intohome-assistant:devfrom
dmulcahey:dm/zha-config-translations-backend

Conversation

@dmulcahey
Copy link
Copy Markdown
Contributor

Proposed change

This PR moves the translations for the ZHA configuration panel sections to the backend so that PR's don't have to be opened in Both the frontend and backend repos when new configuration panel sections are added.

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: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:

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 @Adminiuga, mind taking a look at this pull request as its been labeled with an integration (zha) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

Copy link
Copy Markdown
Contributor

@Adminiuga Adminiuga left a comment

Choose a reason for hiding this comment

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

Lgtm

"single_instance_allowed": "[%key:common::config_flow::abort::single_instance_allowed%]"
}
},
"config_panel": {
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 think that this makes sense as long as the actual panel code lives in the frontend. Or are these strings passed to the frontend from the backend?

CC @bramkragten

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.

They use ha-form and get the actual data/fields from the backend, so I think it makes sense to have the translations on the backend.

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.

@balloob are we good with this now?

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.

Yes

@dmulcahey dmulcahey added this to the 2021.5.0 milestone Apr 30, 2021
@balloob balloob merged commit 4ed74cd into home-assistant:dev Apr 30, 2021
@github-actions github-actions bot locked and limited conversation to collaborators May 1, 2021
@dmulcahey dmulcahey deleted the dm/zha-config-translations-backend branch December 18, 2021 12:24
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.

5 participants