Skip to content
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

Update docs for home-assistant/core#123427 #34220

Merged
merged 2 commits into from
Oct 25, 2024

Conversation

jbergler
Copy link
Contributor

@jbergler jbergler commented Aug 9, 2024

Proposed change

home-assistant/core#123427 extends support for wait.completed to wait_for_trigger (rather than just wait_template)

This updates the docs to reflect that, and orders the attributes so that the always present ones are first in the list.
(which also happens to be alphabetical)

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

  • Documentation
    • Enhanced clarity and detail regarding wait and wait_for_trigger actions, including explanations of wait.completed and wait.trigger.
    • Elaborated on the timeout feature for wait_template and wait_for_trigger, with updated examples.
    • Expanded section on repeat actions, including new examples and the introduction of the repeat loop variable.
    • Improved guidance on if-then and choose actions with comprehensive examples.

@home-assistant home-assistant bot added has-parent This PR has a parent PR in a other repo next This PR goes into the next branch labels Aug 9, 2024
Copy link
Contributor

coderabbitai bot commented Aug 9, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The documentation for the Home Assistant Script Syntax has been revised to enhance clarity and detail. Key updates include explanations of the wait and wait_for_trigger actions, specifically the creation of the wait variable and its properties. The timeout feature for wait_template and wait_for_trigger has been elaborated, along with expanded examples for repeat, if-then, and choose actions. These modifications aim to provide a more comprehensive understanding of the script syntax and its functionalities.

Changes

Files Change Summary
source/_docs/scripts.markdown Enhanced explanations for wait, wait_for_trigger, timeout, and expanded examples for repeat, if-then, and choose actions.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant System
    participant Trigger

    User->>System: Initiate wait_template
    System-->>User: wait.completed available
    User->>Trigger: Trigger event
    Trigger-->>System: Trigger event received
    System-->>User: wait.trigger available
Loading

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Aug 9, 2024

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit b06a13a
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/671918e483bf28000818fa34
😎 Deploy Preview https://deploy-preview-34220--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

🧹 Outside diff range and nitpick comments (1)
source/_docs/scripts.markdown (1)

284-286: Consider adding a practical example of wait.completed usage.

While the documentation is clear, adding a practical example showing how to use wait.completed with wait_for_trigger would help users better understand the feature. For example:

# Example: Using wait.completed with wait_for_trigger
- wait_for_trigger:
    - trigger: state
      entity_id: binary_sensor.motion
      to: "on"
  timeout: 00:01:00
- if:
    - condition: template
      value_template: "{{ wait.completed }}"
  then:
    - service: notify.notify
      data:
        message: "Motion detected within timeout"
  else:
    - service: notify.notify
      data:
        message: "No motion detected within timeout"
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 17ecb9f and b06a13a.

📒 Files selected for processing (1)
  • source/_docs/scripts.markdown (1 hunks)
🧰 Additional context used
🔇 Additional comments (2)
source/_docs/scripts.markdown (2)

284-286: LGTM! Clear documentation of wait variable attributes.

The documentation clearly explains the new wait.completed support and maintains good organization with alphabetically ordered attributes.


284-286: Documentation aligns perfectly with PR objectives.

The changes successfully document the wait.completed support for wait_for_trigger while maintaining the desired alphabetical ordering of attributes.

Copy link
Contributor

@c0ffeeca7 c0ffeeca7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @jbergler 👍

@c0ffeeca7 c0ffeeca7 merged commit 817d23f into home-assistant:next Oct 25, 2024
7 checks passed
@home-assistant home-assistant bot removed the parent-merged The parent PR has been merged already label Oct 25, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Oct 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
has-parent This PR has a parent PR in a other repo next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants