Add details around configuration and options flow#12239
Conversation
There was a problem hiding this comment.
Some small things provided as suggestions.
In general, I think we should avoid the terms "configuration flow" or "options flow", these are terms used internally as developers. However, users aren't familiar with those terms, nor are they listed anywhere. In general, we refer to the "UI", "web interface" or the Home Assistant (web) frontend.
Co-Authored-By: Franck Nijhof <frenck@frenck.nl>
Co-Authored-By: Franck Nijhof <frenck@frenck.nl>
Co-Authored-By: Franck Nijhof <frenck@frenck.nl>
Co-Authored-By: Franck Nijhof <frenck@frenck.nl>
Co-Authored-By: Franck Nijhof <frenck@frenck.nl>
Co-Authored-By: Franck Nijhof <frenck@frenck.nl>
Co-Authored-By: Franck Nijhof <frenck@frenck.nl>
Thank you for the clean up suggestions. I'll go through and replace up some of the technical terms (configuration.yaml) as well. |
@frenck The latest commit removes the technical terminology. Let me know if you see anything else. |
Proposed change
This PR adds missing details for the Konnected.io configuration flow based setup that was released in 0.106.
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.