-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Add documentation for new services for bosch_alarm #38368
base: next
Are you sure you want to change the base?
Conversation
It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the |
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
📝 WalkthroughWalkthroughThe pull request updates the Bosch Alarm integration documentation by adding an "Actions" section. Within this section, a new action titled "Set panel date and time" is detailed. The action description includes a table with two data attributes: Changes
Sequence Diagram(s)sequenceDiagram
participant U as User
participant I as Bosch Alarm Integration
participant P as Alarm Panel
U->>I: Request "Set panel date and time" with config_entry_id & (optional) datetime
I->>I: Validate required parameters (config_entry_id)
I->>P: Set panel date and time (apply provided datetime or default current datetime)
P-->>I: Acknowledge update
I-->>U: Return success response
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (3)
source/_integrations/bosch_alarm.markdown (3)
42-42
: Remove trailing whitespace on line 42.Line 42 contains trailing spaces. Removing these will help comply with Markdown linting rules (MD009) and keep the file clean.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
42-42: Trailing spaces
Expected: 0 or 2; Actual: 1(MD009, no-trailing-spaces)
48-48
: Eliminate trailing spaces on line 48.Line 48 also has trailing whitespace. Please remove it to maintain consistent Markdown style.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
48-48: Trailing spaces
Expected: 0 or 2; Actual: 1(MD009, no-trailing-spaces)
43-53
: New "Actions" Section Documentation Looks Good.The newly added "Actions" section—which details the "Set panel date and time" action—is clear and well structured. The table correctly indicates that:
config_entry_id
is required (by marking it as not optional), anddatetime
is optional with a default to the current date and time if omitted.For enhanced clarity, consider noting the accepted format for the
datetime
attribute if there’s a specific expected format (or linking to additional details). Overall, this addition aligns well with the PR objectives.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
48-48: Trailing spaces
Expected: 0 or 2; Actual: 1(MD009, no-trailing-spaces)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
source/_integrations/bosch_alarm.markdown
(1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/_integrations/bosch_alarm.markdown
42-42: Trailing spaces
Expected: 0 or 2; Actual: 1
(MD009, no-trailing-spaces)
48-48: Trailing spaces
Expected: 0 or 2; Actual: 1
(MD009, no-trailing-spaces)
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
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.
Actionable comments posted: 0
🧹 Nitpick comments (2)
source/_integrations/bosch_alarm.markdown (2)
51-54
: List Indentation Adjustment for 'config_entry_id'
The nested bullet points for the Data attributeconfig_entry_id
are indented with three spaces, but markdownlint expects two spaces. Adjusting this will improve readability on mobile devices.- - **Description**: The ID of the config entry to get the schedule from. - - **Optional**: No + - **Description**: The ID of the config entry to get the schedule from. + - **Optional**: No🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
52-52: Unordered list indentation
Expected: 2; Actual: 3(MD007, ul-indent)
53-53: Unordered list indentation
Expected: 2; Actual: 3(MD007, ul-indent)
55-58
: List Indentation Adjustment for 'datetime'
Similarly, the nested bullet points for the Data attributedatetime
use a three-space indentation. Please update lines 56 and 57 to use two spaces to comply with MD007 guidelines from markdownlint.- - **Description**: The date and time to set. Defaults to the current date and time if it is not set. - - **Optional**: Yes + - **Description**: The date and time to set. Defaults to the current date and time if it is not set. + - **Optional**: Yes🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
56-56: Unordered list indentation
Expected: 2; Actual: 3(MD007, ul-indent)
57-57: Unordered list indentation
Expected: 2; Actual: 3(MD007, ul-indent)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
source/_integrations/bosch_alarm.markdown
(1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/_integrations/bosch_alarm.markdown
52-52: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
53-53: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
56-56: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
57-57: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
🔇 Additional comments (2)
source/_integrations/bosch_alarm.markdown (2)
43-46
: Clear Action Section Introduction
The newly added "Actions" section is well integrated into the document and clearly introduces the new Bosch Alarm action. No issues found here.
47-50
: Accurate and Informative Action Documentation
The "Set panel date and time" action is documented with clarity, explaining its purpose and usage effectively. Ensure that the style and terminology remain consistent with other integration documentation in the project.
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.
Thank you, @sanjay900 👍
Proposed change
Add documentation for date and time service for bosch alarm
Type of change
current
branch).current
branch).next
branch).next
branch).Additional information
Checklist
current
branch.next
branch.Summary by CodeRabbit