Skip to content

Fixed the cmps abbreviation #39757

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 28, 2025
Merged

Conversation

sanchosk
Copy link
Contributor

@sanchosk sanchosk commented Jun 28, 2025

The abbreviation is listed as cmp, but it should be cmps. The examples are OK, just the text description above example is not.

Proposed change

Just a small change to fix the docs - the descriptive text is missing letter s from cmps abbreviation explanation.

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
    • Corrected the abbreviation for component-specific options in MQTT device discovery payloads from "cmp" to "cmps" in both descriptive text and example JSON payloads.

The abbreviation is listed as `cmp`, but it should be `cmps`. The examples are OK, just the text description above example is not.
@home-assistant home-assistant bot added the current This PR goes into the current branch label Jun 28, 2025
Copy link

netlify bot commented Jun 28, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 018524c
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/685fd1c32630b10008e9fc6a
😎 Deploy Preview https://deploy-preview-39757--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 28, 2025

📝 Walkthrough

Walkthrough

The documentation for MQTT device discovery was updated to correct the abbreviation for the key holding component-specific options, changing it from cmp to cmps in both the descriptive text and example JSON payloads. No functional or structural changes were made to the codebase.

Changes

File(s) Change Summary
source/_integrations/mqtt.markdown Updated documentation to use cmps instead of cmp for component-specific options in MQTT device discovery payloads.

Sequence Diagram(s)

No sequence diagram generated as the changes are limited to documentation updates.


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: 1

📜 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 a77e17e and 018524c.

📒 Files selected for processing (1)
  • source/_integrations/mqtt.markdown (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`source/_integrations/*`: Integration documentation must use the provided template structure and section order.

source/_integrations/*: Integration documentation must use the provided template structure and section order.

📄 Source: CodeRabbit Inference Engine (.github/copilot-instructions.md)

List of files the instruction was applied to:

  • source/_integrations/mqtt.markdown
⏰ 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

Comment on lines +373 to 376
The component specific options are placed as mappings under the `components` key (abbreviated as `cmps`) like:

```json
{
Copy link
Contributor

@coderabbitai coderabbitai bot Jun 28, 2025

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Abbreviation updated here but still inconsistent further down

Line 373 correctly switches the abbreviation to cmps, yet several subsequent references (e.g. line 412 & line 572) still mention cmp. Readers will be confused by mixed usage.

Please align the entire document to cmps, e.g.:

- The components id's under the `components` (`cmp`) key, are used as part of the discovery identification.
+ The component IDs under the `components` (`cmps`) key are used as part of the discovery identification.

and

- Discovery id: `0AFFD2 bla` *(`0AFFD2`from discovery topic, `bla`: The key under `cmp` in the discovery payload)*
+ Discovery id: `0AFFD2 bla` *(`0AFFD2` from discovery topic, `bla`: The key under `cmps` in the discovery payload)*

Ensuring a single, correct abbreviation prevents implementation errors in user payloads.

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In source/_integrations/mqtt.markdown around lines 373 to 376 and further down
near lines 412 and 572, the abbreviation for the components key is
inconsistently used as both `cmps` and `cmp`. To fix this, update all
occurrences of `cmp` to `cmps` throughout the entire document to maintain
consistency and prevent confusion or implementation errors.

Copy link
Contributor

Choose a reason for hiding this comment

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

Addressed in #39762

Copy link
Contributor

Choose a reason for hiding this comment

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

@jbouwh Thank you for addressing the inconsistency! It's great that you created PR #39762 to fix all the mixed usage of cmp vs cmps throughout the document. This will prevent confusion for users implementing MQTT discovery payloads and ensure consistent documentation.


If you found this review helpful, would you consider giving us a shout-out on X?

Thank you for using CodeRabbit!

@silamon silamon enabled auto-merge (squash) June 28, 2025 11:31
@silamon silamon merged commit a40b921 into home-assistant:current Jun 28, 2025
7 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jun 30, 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.

3 participants