-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
To-do list: add note that item can be UID #38704
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
Conversation
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
📝 WalkthroughWalkthroughThe documentation for the Changes
Sequence Diagram(s)📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (3)
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. 🪧 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/todo.markdown (3)
79-90
: Clarify that UIDs are not shown in the UI.
Consider adding a brief note around this response example to explain that theuid
field is only visible via the API (e.g.,todo.get_items
) and does not appear in the Home Assistant frontend. This will help users understand why they won’t see UIDs in the UI.
96-101
: Refine theitem
field description for brevity.
The new description correctly states thatitem
accepts a name/summary or UID. For a cleaner, more active tone, you might rephrase to:
“To find an item’s UID, use thetodo.get_items
action.”
121-128
: Ensure selector link styling is consistent.
The UID guidance in thetodo.update_item
table is on point. Please double-check that the “[Target Selector]” link styling here matches the lowercase “[target selector]” used in other action descriptions to maintain uniformity across the docs.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
source/_integrations/todo.markdown
(3 hunks)
🔇 Additional comments (2)
source/_integrations/todo.markdown (2)
73-73
: Updated example entity_id aligns with PR summary.
Thetodo.get_items
example now usestodo.vacation_preparation
instead oftodo.personal_tasks
, matching the PR's intent. Please verify that this entity is referenced elsewhere or update related sections for consistency.
146-148
: UID guidance correctly applied.
Thetodo.remove_item
table entry now mirrors the UID instruction from other actions, ensuring consistency in how users locate and reference items.
source/_integrations/todo.markdown
Outdated
| `description` | yes | A more complete description than the one provided by the summary. | Collect all necessary documents and submit the final return. | | ||
| Data attribute | Optional | Description | Example | | ||
| -------------- | -------- | ---------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | | ||
| `item` | no | The name/summary or UID of the to-do item. To find the UID of an item, perform a `get_items` action on the to-do list. | `Submit income tax return` or `01244b28-e604-11ee-a0a4-e45f0197c057` | |
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.
Maybe be more specific like I did here home-assistant/core#143556 saying that UID is better to avoid issues. But name can still be use.
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!
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.
I do not know about that, using name is very user friendly and pretty safe as long as you do not have duplicates.
But I am fine with this version regardless
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.
The devil is in the detail here. I'm suggesting that we should encourage to use the UID but name are fine. So if the issue occur people will have read somewhere that they could use UID instead.
For sure it's not UI friendly at all
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.
Then if the devil is in the details, I would say that uuid can be used to dedupe times with the same name in case it's needed
Thank you, @jlpouffier and @TimoPtr 👍 |
Proposed change
To-do list integration: add note that item can be UID
Type of change
current
branch).current
branch).next
branch).next
branch).Additional information
Checklist
current
branch.next
branch.Summary by CodeRabbit
item
field in to-do actions can accept either the name/summary or UID, recommending UID for safety.