-
-
Notifications
You must be signed in to change notification settings - Fork 36.5k
Add description placeholders to service translation strings #154984
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
Conversation
|
Hey there @Julius2342, @farmio, @marvin-w, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
|
Hi 👋!
when loading the frontend. |
|
Oops, I'll do some more investigation. |
|
It seems the API returns the correct translation strings, so I'm not sure what happens here yet. |
Try to clear you frontend cash. It should work after all (CTRL+F5) and restart your browser. |
|
I'm not sure the API changes are needed, this PR removes translations from the old service API #147120 I think that PR should be decided on first, because if it's accepted this PR is much simpler |
69b409f to
b0d611a
Compare
|
The translation placeholders don't seem to be returned in the response to the WS command |
|
Frontend also needs to be updated:
|
emontnemery
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @jbouwh 👍
Can be merged when the frontend PR is approved.
|
@jbouwh, @emontnemery, I started looking into moving URLs out of |
Co-authored-by: Erik Montnemery <[email protected]>
…vice and to async_register_platform_entity_service
6b9af13 to
8d28424
Compare
You are right, that part was missed. Added the support and a test. |
|
I think a good next step would be to make sure we have tooling like we have with issues and entity placeholders to check that we have the right placeholders filled |
|
Proposed change
To avoid URLs in service description strings, we want to be able to move those out of
strings.json. This PR makes it possible to add description placeholders via the service registration.Needs: home-assistant/frontend#27636
Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: