-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Vasttrafik sensor configuration variable style #6414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Change to new style for configuration variables description (#6385).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to quote the description text.
Not description: "The API secret to access your Västtrafik account."
but description: The API secret to access your Västtrafik account.
lines: | ||
description: Only consider these lines. | ||
required: false | ||
type: string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is supposed to be described as a list of strings (list, string
), but home-assistant/developers.home-assistant#104 is not resolved yet.
departures: | ||
description: List of travel routes. | ||
required: true | ||
type: map |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And this may be a list of mappings.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 🐦
Change to new style for configuration variables description.
Related to #6385.
Description:
Update style of Västtrafik sensor documentation to follow new configuration variables description.
Pull request in home-assistant (if applicable): home-assistant/home-assistant#
Checklist:
next
is for changes and new documentation that will go public with the next home-assistant release. Fixes, changes and adjustments for the current release should be created againstcurrent
.