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

Cleanup mqtt publish action template option documentation #34257

Merged
merged 2 commits into from
Aug 12, 2024

Conversation

jbouwh
Copy link
Contributor

@jbouwh jbouwh commented Aug 12, 2024

Proposed change

Cleanup mqtt publish action template option documentation.

This is a follow up on #33854

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
    • Updated MQTT integration documentation to provide illustrative YAML examples for the topic and payload parameters.
    • Clarified that payload must be a string and included guidance on JSON formatting in YAML.
    • Simplified instructions regarding the use of Home Assistant's YAML editor to reduce confusion.

@home-assistant home-assistant bot added current This PR goes into the current branch in-progress This PR/Issue is currently being worked on needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch labels Aug 12, 2024
@home-assistant
Copy link

It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the next branch. Please change the target branch of this PR to next and rebase if needed.

Copy link

netlify bot commented Aug 12, 2024

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 0249077
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/66b9e4166bab740008d7b4ea
😎 Deploy Preview https://deploy-preview-34257--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.

@jbouwh jbouwh added integration: mqtt and removed needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch labels Aug 12, 2024
@home-assistant
Copy link

Hey there @emontnemery, @bdraco, mind taking a look at this feedback as it has been labeled with an integration (mqtt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of mqtt can trigger bot actions by commenting:

  • @home-assistant close Closes the feedback.
  • @home-assistant rename Awesome new title Renames the feedback.
  • @home-assistant reopen Reopen the feedback.
  • @home-assistant unassign mqtt Removes the current integration label and assignees on the feedback, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

@jbouwh jbouwh removed the in-progress This PR/Issue is currently being worked on label Aug 12, 2024
Copy link
Contributor

coderabbitai bot commented Aug 12, 2024

Walkthrough

Walkthrough

The changes to the MQTT integration documentation focus on the mqtt.publish action. Significant modifications include the removal of strict requirements for topic and payload, which have been replaced with illustrative examples. The documentation now clarifies that payload must be a string and simplifies previous warnings about YAML formatting, aiming for a more user-friendly presentation. However, this shift may obscure critical usage constraints.

Changes

Files Change Summary
source/_integrations/mqtt.markdown Removed strict instructions for topic and payload, added YAML examples, clarified payload must be a string, and simplified YAML editor warnings.

Assessment against linked issues

Objective Addressed Explanation
Update payload_template documentation
Clarify usage of topic and payload The removal of specific requirements may lead to confusion regarding usage constraints.

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

@home-assistant home-assistant bot added in-progress This PR/Issue is currently being worked on needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch labels Aug 12, 2024
@home-assistant
Copy link

It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the next branch. Please change the target branch of this PR to next and rebase if needed.

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, codebase verification and nitpick comments (2)
source/_integrations/mqtt.markdown (2)

Line range hint 1113-1132:
Clarify the use of payload and payload_template.

The examples provided for mqtt.publish are helpful, but they should explicitly mention the constraints regarding the use of payload and payload_template. Users should be aware that both cannot be used simultaneously.

Consider adding a note to emphasize this constraint to prevent potential misuse.

Tools
LanguageTool

[typographical] ~1139-~1139: Consider adding a comma.
Context: ... want to send JSON using the YAML editor then you need to format/escape it properly. ...

(IF_THEN_COMMA)


Line range hint 1149-1167:
Ensure consistency in example formatting.

The example provided for publishing a temperature sensor is well-structured. Ensure that similar examples throughout the documentation maintain consistent formatting and detail level.

No changes needed here, but keep this consistency in mind for future documentation updates.

Tools
LanguageTool

[typographical] ~1139-~1139: Consider adding a comma.
Context: ... want to send JSON using the YAML editor then you need to format/escape it properly. ...

(IF_THEN_COMMA)

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, codebase verification and nitpick comments (1)
source/_integrations/mqtt.markdown (1)

1138-1142: Clarification on payload format is helpful.

The note that payload must be a string and the guidance on JSON formatting are crucial for user understanding.

Consider adding a comma for clarity.

A comma after "YAML editor" would improve readability.

- If you want to send JSON using the YAML editor then you need to format/escape
+ If you want to send JSON using the YAML editor, then you need to format/escape
Tools
LanguageTool

[typographical] ~1139-~1139: Consider adding a comma.
Context: ... want to send JSON using the YAML editor then you need to format/escape it properly. ...

(IF_THEN_COMMA)

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, @jbouwh 👍

@c0ffeeca7 c0ffeeca7 removed in-progress This PR/Issue is currently being worked on needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch labels Aug 12, 2024
@c0ffeeca7 c0ffeeca7 merged commit eb55aff into current Aug 12, 2024
8 checks passed
@c0ffeeca7 c0ffeeca7 deleted the mqtt-cleanup-publish-template-options-remains branch August 12, 2024 12:17
YogevBokobza pushed a commit to YogevBokobza/home-assistant.io that referenced this pull request Aug 12, 2024
…tant#34257)

* Cleanup mqtt publish action template option documentation

* Missed instance
@github-actions github-actions bot locked and limited conversation to collaborators Aug 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
by-code-owner current This PR goes into the current branch integration: mqtt
Projects
None yet
Development

Successfully merging this pull request may close these issues.

payload_template doc requires updating
4 participants