mirror of
https://github.com/home-assistant/developers.home-assistant.git
synced 2025-07-19 15:26:29 +00:00
Fix use of incorrect variable type (#781)
This commit is contained in:
parent
cc2f367ac9
commit
f71271b944
@ -20,7 +20,7 @@ To ensure that the documentation for Home Assistant is consistent and easy to fo
|
|||||||
- Configuration variables must document the requirement status (`false` or `true`).
|
- Configuration variables must document the requirement status (`false` or `true`).
|
||||||
- Configuration variables must document the default value, if any.
|
- Configuration variables must document the default value, if any.
|
||||||
- Configuration variables must document the accepted value types (see [Configuration variables details](documenting/create-page.md#configuration)).
|
- Configuration variables must document the accepted value types (see [Configuration variables details](documenting/create-page.md#configuration)).
|
||||||
- For configuration variables that accept multiple types, separate the types with a comma (i.e. `string, int`).
|
- For configuration variables that accept multiple types, separate the types with a comma (i.e. `string, integer`).
|
||||||
- Use YAML sequence syntax in the sample code if it is supported.
|
- Use YAML sequence syntax in the sample code if it is supported.
|
||||||
- All examples should be formatted to be included in `configuration.yaml` unless explicitly stated.
|
- All examples should be formatted to be included in `configuration.yaml` unless explicitly stated.
|
||||||
- Use capital letters and `_` to indicate that the value needs to be replaced. E.g., `api_key: YOUR_API_KEY` or `api_key: REPLACE_ME`.
|
- Use capital letters and `_` to indicate that the value needs to be replaced. E.g., `api_key: YOUR_API_KEY` or `api_key: REPLACE_ME`.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user