jeans/developers.home-assistant
jeans/developers.home-assistant
1
0
Fork 0
mirror of https://github.com/home-assistant/developers.home-assistant.git synced 2025-07-12 20:06:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update development_tips.md for localization (#2650)

Browse Source 
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
This commit is contained in:
John Hillery 2025-04-23 16:59:19 -04:00 committed by GitHub
parent 48eaa9ed26
commit 8d0a224d3e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/development_tips.md
View File

@ -16,7 +16,13 @@ See the [API library docs](api_lib_index#trying-your-library-inside-home-assista
### Test Core integration changes in your production Home Assistant environment
If you made a change to a core integration and you want to test it in your production Home Assistant environment, copy the integration folder into `/config/custom_components`, add a version to the `manifest.json` (e.g. "version": "0.0.0"), and restart Home Assistant. Home Assistant will always prioritize integrations in `custom_components` over the core integration. Don't forget to remove it once you are done testing; otherwise, you will be stuck on that version.
To test a core integration change in your production Home Assistant environment:
1. Copy the integration folder into `/config/custom_components`.
2. Add a **version** field to `manifest.json` (for example, `"version": "0.0.0"`).
3. If the integration uses localized strings, copy `strings.json` into `translations/en.json` under the integration folder as described in [Custom integration localization](internationalization/custom_integration).
4. Restart Home Assistant.
Home Assistant will always prioritize integrations in `custom_components` over the core integration. Don't forget to remove it once you are done testing; otherwise, you will be stuck on that version.
### When adding a config flow to an integration, be aware of the frontend