From 40559d240576aa41169649fe9c5587e571d44f44 Mon Sep 17 00:00:00 2001 From: Teemu R Date: Thu, 16 Feb 2023 23:40:24 +0100 Subject: [PATCH] Clarify config flow step definitions (#1683) * Clarify config flow step definitions * Update docs/config_entries_config_flow_handler.md Co-authored-by: Martin Hjelmare --------- Co-authored-by: Martin Hjelmare --- docs/config_entries_config_flow_handler.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/config_entries_config_flow_handler.md b/docs/config_entries_config_flow_handler.md index 57d68f3d..d8d84c2f 100644 --- a/docs/config_entries_config_flow_handler.md +++ b/docs/config_entries_config_flow_handler.md @@ -32,7 +32,7 @@ Once you have updated your manifest and created the `config_flow.py`, you will n ## Defining steps -Your config flow will need to define steps of your configuration flow. The docs for [Data Entry Flow](data_entry_flow_index.md) describe the different return values of a step. Here is an example on how to define the `user` step. +Your config flow will need to define steps of your configuration flow. Each step is identified by a unique step name (`step_id`). The step callback methods follow the pattern `async_step_`. The docs for [Data Entry Flow](data_entry_flow_index.md) describe the different return values of a step. Here is an example of how to define the `user` step: ```python import voluptuous as vol