8000 Update todo.md for `completed` field by karwosts · Pull Request #2683 · home-assistant/developers.home-assistant · GitHub
[go: up one dir, main page]

Skip to content

Update todo.md for completed field #2683

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

Closed
wants to merge 2 commits into from
Closed

Update todo.md for completed field #2683

wants to merge 2 commits into from

Conversation

karwosts
Copy link
Contributor
@karwosts karwosts commented May 28, 2025

Proposed change

For home-assistant/core#145820

Type of change

  • Document existing features within Home Assistant
  • Document new or changing features for which there is an existing pull request elsewhere
  • Spelling or grammatical corrections, or rewording for improved clarity
  • Changes to the backend of this documentation
  • Remove stale or deprecated documentation

Checklist

  • I have read and followed the documentation guidelines.
  • I have verified that my changes render correctly in the documentation.

Additional information

Summary by CodeRabbit

  • Documentation
    • Updated documentation for to-do items to include a new optional field indicating when an item was last marked as complete.

Copy link
Contributor
coderabbitai bot commented May 28, 2025
📝 Walkthrough

Walkthrough

The documentation for the TodoItem entity was updated to include a new optional field, completed, which records the timestamp when a to-do item was last marked as complete. No other fields or their descriptions were changed.

Changes

File Change Summary
docs/core/entity/todo.md Added documentation for new optional completed field to TodoItem entity.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant TodoItem (Entity Doc)
    User->>TodoItem (Entity Doc): Reads property list
    TodoItem (Entity Doc)-->>User: Returns properties including new 'completed' field
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 (1)
docs/core/entity/todo.md (1)

117-117: Fix table formatting for the new completed row.
The added row is missing the trailing pipe and has an extra space inside the <code> tag, which breaks the table styling.

-| completed | <code> datetime.datetime &#124; None</code> | `None` | A timestamp indicating the time this item was last marked `COMPLETE`.
+| completed | <code>datetime.datetime &#124; None</code> | `None` | A timestamp indicating the time this item was last marked `COMPLETE`. |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

117-117: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe

(MD055, table-pipe-style)

📜 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 9822f0f and 3c0824d.

📒 Files selected for processing (1)
  • docs/core/entity/todo.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/core/entity/todo.md

117-117: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe

(MD055, table-pipe-style)

🔇 Additional comments (1)
docs/core/entity/todo.md (1)

1-118: Verify rendering of the updated field.
Please preview the documentation site to ensure the new completed field displays correctly in the table and adheres to Home Assistant’s docs formatting guidelines.

🧰 Tools
🪛 LanguageTool

[grammar] ~7-~7: It appears that a hyphen is missing in the noun “to-do” (= task) or did you mean the verb “to do”?
Context: ...A To-do list entity is derived from the [homeassistant.components.todo.TodoListEntity](https://github.com/hom...

(TO_DO_HYPHEN)


[grammar] ~17-~17: It appears that a hyphen is missing in the noun “to-do” (= task) or did you mean the verb “to do”?
Context: ...----------------------------------- | | todo_items | list[TodoItem] | Non...

(TO_DO_HYPHEN)

🪛 markdownlint-cli2 (0.17.2)

112-112: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe

(MD055, table-pipe-style)


113-113: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe

(MD055, table-pipe-style)


114-114: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe

(MD055, table-pipe-style)


115-115: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe

(MD055, table-pipe-style)


116-116: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe

(MD055, table-pipe-style)


117-117: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe

(MD055, table-pipe-style)

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 (1)
docs/core/entity/todo.md (1)

117-117: Add missing trailing pipe in the new table row
The added completed row is missing the closing |, causing an inconsistency with the table‐pipe style (MD055). Please append a | at the end of the row to match the existing format.

Verify documentation rendering
Since doc changes haven’t been previewed yet, please build or preview the site to ensure the new field displays correctly.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

117-117: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe

(MD055, table-pipe-style)

📜 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 3c0824d and f9c328f.

📒 Files selected for processing (1)
  • docs/core/entity/todo.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/core/entity/todo.md

117-117: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe

(MD055, table-pipe-style)

@karwosts karwosts marked this pull request as draft June 9, 2025 12:52
@karwosts karwosts closed this Jul 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0