Upstream/esphome-docs
1
0
Fork 0
mirror of https://github.com/esphome/esphome-docs.git synced 2025-01-28 22:42:05 +01:00
Code Issues Projects Releases Wiki Activity

Consistent spelling of "ID" (#1068)

Browse Source
This commit is contained in:
Philip Allgaier 2021-03-22 20:16:55 +01:00 committed by GitHub
parent dc4f985548
commit d13e363702
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
guides/configuration-types.rst
View File

@ -13,15 +13,15 @@ page describes them.
ID
--
Quite an important aspect of ESPHome are “ids”. They are used to
Quite an important aspect of ESPHome are “IDs”. They are used to
connect components from different domains. For example, you define an
output component together with an id and then later specify that same id
output component together with an ID and then later specify that same ID
in the light component. IDs should always be unique within a
configuration and ESPHome will warn you if you try to use the same
ID twice.
Because ESPHome converts your configuration into C++ code and the
ids are in reality just C++ variable names, they must also adhere to
IDs are in reality just C++ variable names, they must also adhere to
C++’s naming conventions. `C++ Variable
names <https://venus.cs.qc.cuny.edu/~krishna/cs111/lectures/D3_C++_Variables.pdf>`__
…
@ -224,7 +224,7 @@ of nodes inherit:
To hide these base files from the dashboard, you can
- Place them in a subdirectory (dashboard only shows files in top-level dir)
- Place them in a subdirectory (dashboard only shows files in top-level directory)
- Prepend a dot to the filename, like ``.base.yaml``
.. _command-line-substitutions:
@ -290,8 +290,8 @@ config in the main yaml file. All definitions from packages will be merged with
config in non-destructive way so you could always override some bits and pieces of package
configuration.
Consider the following example where author put common pieces of configuration like WiFi,
I²C into base files and extends it with some devices specific configurations in the main config.
Consider the following example where the author put common pieces of configuration like WiFi and
I²C into base files and extends it with some device specific configurations in the main config.
Note how the piece of configuration describing ``api`` component in ``device_base.yaml`` gets
merged with the services definitions from main config file.