From 364a8ef5141e27d7465f550176f8698e6909cbcb Mon Sep 17 00:00:00 2001 From: Sean Hoyt Date: Thu, 30 Jun 2022 16:43:39 -0500 Subject: [PATCH] Fix manifest version tag example (#1381) --- docs/development_tips.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/development_tips.md b/docs/development_tips.md index cdf74a7c..83810032 100644 --- a/docs/development_tips.md +++ b/docs/development_tips.md @@ -16,7 +16,7 @@ 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"), 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. +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. ### When adding a config flow to an integration, be aware of the frontend