mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-05-01 08:47:35 +00:00

* Spelling fixes * "It's" -> "its" fixes * Fix capitalization of "Pi" in "Raspberry Pi" "Pi", not "PI" or "pi".
1.7 KiB
1.7 KiB
layout | title | description | date | sidebar | comments | sharing | footer |
---|---|---|---|---|---|---|---|
page | Checklist for creating a component | A list of things to pay attention to when code reviewing a component. | 2017-01-15 14:09 -0800 | true | false | true | true |
A checklist of things to do when you're adding a new component.
Not all existing platforms follow the requirements in this checklist. This cannot be used as a reason to not follow them!
{% linkable_title 1. Requirements %}
- Requirement version pinned:
REQUIREMENTS = ['phue==0.8.1']
- We no longer want requirements hosted on GitHub. Please upload to PyPi.
- Requirements should only be imported inside functions. This is necessary because requirements are installed on the fly.
{% linkable_title 2. Configuration %}
- Voluptuous schema present for config validation
- Default parameters specified in voluptuous schema, not in
setup(…)
- Schema using as many generic config keys as possible from
homeassistant.const
- If your component has platforms, define a
PLATFORM_SCHEMA
instead of aCONFIG_SCHEMA
. - If using a
PLATFORM_SCHEMA
to be used withEntityComponent
, import base fromhomeassistant.helpers.config_validation
- Never depend on users adding things to
customize
to configure behavior inside your component.
{% linkable_title 3. Component/platform communication %}
- If you need to share global data with platforms, use the dictionary
hass.data
.hass.data[DATA_XY]
whileXY
is the component is preferred overhass.data[DOMAIN]
. - If the component fetches data that causes its related platform entities to update, you can notify them using the dispatcher code in
homeassistant.helpers.dispatcher
.