8000 Use common WWHA doc structure for Third Reality by abmantis · Pull Request #39579 · home-assistant/home-assistant.io · GitHub
[go: up one dir, main page]

Skip to content

Use common WWHA doc structure for Third Reality #39579

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

Merged
merged 1 commit into from
Jun 17, 2025
Merged

Conversation

abmantis
Copy link
Member
@abmantis abmantis commented Jun 16, 2025

Proposed change

This moves the common text we use for WWHA to a common file, so that we can just include it.
Updated Third Reality as a trial. I'll update the rest in follow-up PRs.

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

  • Link to parent pull request in the codebase:
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue: fixes #

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
    • Introduced a standardized description template for "Works with Home Assistant" partner integrations.
    • Updated the Third Reality integration page to use the new template, providing a concise and consistent summary with supported protocols and direct links to documentation.

@home-assistant home-assistant bot added the current This PR goes into the current branch label Jun 16, 2025
Copy link
netlify bot commented Jun 16, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit c2659ce
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/685044f0a93ae400082c9f2e
😎 Deploy Preview https://deploy-preview-39579--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 project configuration.

Copy link
Contributor
coderabbitai bot commented Jun 16, 2025
📝 Walkthrough

Walkthrough

A new shared markdown include file was introduced to standardize integration descriptions for the "Works with Home Assistant" program. The Third Reality integration documentation was updated to use this include, replacing its detailed content with a templated summary generated by the new snippet.

Changes

File(s) Change Summary
source/_includes/integrations/wwha.md Added a new Liquid template snippet for generating standardized partner integration descriptions.
source/_integrations/third_reality.markdown Replaced detailed integration content with an include directive referencing the new shared snippet.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HomeAssistantDocs
    participant WWHAInclude

    User ->> HomeAssistantDocs: Request Third Reality integration page
    HomeAssistantDocs ->> WWHAInclude: Render integration description (with protocols, URL)
    WWHAInclude -->> HomeAssistantDocs: Return standardized summary with badges and links
    HomeAssistantDocs -->> User: Serve rendered integration documentation
Loading

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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
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

🧹 Nitpick comments (3)
source/_includes/integrations/wwha.md (2)

4-18: Simplify list formatting with Liquid filters.

The manual loop and string appends work but can be streamlined using Liquid’s array_to_sentence_string (or a combination of map/join) to handle commas and “and” logic in one go. This will reduce boilerplate and improve readability.


47-47: Ensure file ends with a newline.

Add a trailing newline to satisfy POSIX conventions and avoid potential parser issues.

source/_integrations/third_reality.markdown (1)

31-31: Leverage shared WWHA include; suppress bare-URL lint warning.

The include replaces verbose content nicely. To avoid MD034 (no-bare-urls) on the raw URL, wrap it in angle brackets or disable the rule locally:

<!-- markdownlint-disable MD034 -->
{% include integrations/wwha.md url="https://3reality.com/" %}
<!-- markdownlint-enable MD034 -->
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 99e5e3a and c2659ce.

📒 Files selected for processing (2)
  • source/_includes/integrations/wwha.md (1 hunks)
  • source/_integrations/third_reality.markdown (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/_integrations/third_reality.markdown

31-31: Bare URL used
null

(MD034, no-bare-urls)

🪛 LanguageTool
source/_includes/integrations/wwha.md

[grammar] ~6-~6: Did you mean “Z-Wave” (= wireless protocol)?
Context: ..._with %} {% case type %} {% when "zwave" %}{% assign formatted_type = "Z-Wave" ...

(Z_WAVE)


[grammar] ~22-~22: Did you mean “Z-Wave” (= wireless protocol)?
Context: ...stant. {% if page.works_with contains "zwave" %} {{ name }} Z-Wave devices work lo...

(Z_WAVE)


[grammar] ~25-~25: Did you mean “Z-Wave” (= wireless protocol)?
Context: ...stantly in Home Assistant. {% my add_zwave_device badge domain=page.ha_domain %} ...

(Z_WAVE)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - home-assistant-docs
  • GitHub Check: Header rules - home-assistant-docs
  • GitHub Check: Pages changed - home-assistant-docs
🔇 Additional comments (5)
source/_includes/integrations/wwha.md (5)

1-3: Correctly capturing integration name and URL.

The capture tags with a sensible default for include.name ensure flexibility and prevent errors when name isn’t passed.


20-20: Approve lead paragraph output.

The templated sentence cleanly injects name, url, and the aggregated formatted_types, ensuring consistent wording across integrations.


22-29: Approve Z-Wave conditional section.

The Z-Wave block correctly checks page.works_with, uses the badge helper, and maintains proper “Z-Wave” spelling.


31-38: Approve Zigbee conditional section.

The Zigbee block mirrors the Z-Wave pattern, correctly handling badges and links.


40-46: Approve Matter conditional section.

The Matter section follows the established pattern and correctly integrates badges and documentation links.

@abmantis abmantis changed the title Move common WWHA structure and update Third Reality Use common WWHA doc structure for Third Reality Jun 16, 2025
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.

Nice! Thank you, @abmantis 👍

@c0ffeeca7 c0ffeeca7 merged commit a314ec2 into current Jun 17, 2025
9 checks passed
@c0ffeeca7 c0ffeeca7 deleted the wwha_common_include branch June 17, 2025 03:44
@github-actions github-actions bot locked and limited conversation to collaborators Jun 18, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
current This PR goes into the current branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0