Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Todoist documentation of new features #39437

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

Open
wants to merge 1 commit into
base: next
Choose a base branch
from

Conversation

claytonjn
Copy link
Contributor

@claytonjn claytonjn commented Jun 8, 2025

Proposed change

Document the following new features:

  • Create Todoist section if it doesn't already exist: This adds functionality so that a user can specify a task section that doesn't exist and it will be automatically created. Motivation for this feature is so that Todoist tasks can be created when devices' battery is low and can be placed in a section corresponding to the device area, regardless of whether a corresponding section had been created manually in Todoist.
  • Allow and ignore None for Todoist section: Also to support the use-case of creating a task in a Home Assistant device area; a given device might not be assigned to an area; in that case None will be set for section and it will be ignored, as if no section was specified.
  • Support specifying specific users for reminders: Currently reminders get assigned to the user that Home Assistant is authenticated as. In our household different family members each have their own Todoist account, and we collaborate in shared projects. This adds the ability to assign reminders to any users in the project. Again to support creation of low-battery tasks, this allows me to create reminders for both my wife and I.
  • Support location-based reminders: Exposes ability to specify latitude/longitude or simply a Home Assistant zone and be notified about a task when entering or leaving that location. Note that this shares the provided lat/long or zone location lat/long with Todoist.

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
    • Expanded documentation for the Todoist integration's task creation, detailing new optional parameters for section creation and location-based reminders.
    • Clarified usage of section and reminder parameters, including support for specifying reminder zones, location details, trigger directions, and multiple users.

@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 next This PR goes into the next branch labels Jun 8, 2025
@home-assistant
Copy link

home-assistant bot commented Jun 8, 2025

It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the current branch. Please change the target branch of this PR to current and rebase if needed. If this is documentation for a new feature, please add a link to that PR in your description.

Copy link

netlify bot commented Jun 8, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit e29795f
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/68463d34af2a94000838474b
😎 Deploy Preview https://deploy-preview-39437--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.

@home-assistant home-assistant bot added has-parent This PR has a parent PR in a other repo and removed needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch labels Jun 8, 2025
Copy link
Contributor

coderabbitai bot commented Jun 8, 2025

📝 Walkthrough

Walkthrough

The documentation for the Todoist integration's task creation action has been updated to include new optional parameters for more precise control over section creation and to support location-based reminders. Additions and clarifications cover section handling, reminder zones, location details, direction of reminder triggers, and specifying users for reminders.

Changes

File(s) Change Summary
source/_integrations/todoist.markdown Expanded documentation for todoist.new_task with new optional parameters: section creation control, location-based reminder options, and reminder user specification.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HomeAssistant
    participant Todoist

    User->>HomeAssistant: Call todoist.new_task with parameters
    HomeAssistant->>Todoist: Check if section exists
    alt section does not exist and create_section is true/unspecified
        HomeAssistant->>Todoist: Create section
    end
    HomeAssistant->>Todoist: Create new task in section
    alt reminder parameters provided
        HomeAssistant->>Todoist: Add reminder (zone or location-based)
        alt reminder_users specified
            HomeAssistant->>Todoist: Assign reminder to specified users
        else
            HomeAssistant->>Todoist: Assign reminder to authenticated user
        end
    end
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 (5)
source/_integrations/todoist.markdown (5)

193-193: Fix article use and punctuation in section description.

Add the missing definite article and comma for clarity.

- **section** (*Optional*): The section within the project to add the task to. If section doesn't already exist it will be created (unless `create_section` is `false`).
+ **section** (*Optional*): The section within the project to add the task to. If the section doesn't already exist, it will be created (unless `create_section` is `false`).
🧰 Tools
🪛 LanguageTool

[uncategorized] ~193-~193: You might be missing the article “a” here.
Context: ...thin the project to add the task to. If section doesn't already exist it will be create...

(AI_EN_LECTOR_MISSING_DETERMINER_A)


[typographical] ~193-~193: It seems that a comma is missing.
Context: ...the task to. If section doesn't already exist it will be created (unless `create_sect...

(IF_COMMA)


195-195: Remove unnecessary comma in create_section description.

The comma before if is not needed and interrupts flow.

- **create_section** (*Optional*): Whether the specified section should be created, if it doesn't already exist.
+ **create_section** (*Optional*): Whether the specified section should be created if it doesn't already exist.
🧰 Tools
🪛 LanguageTool

[typographical] ~195-~195: Usually, there’s no comma before “if”.
Context: ... the specified section should be created, if it doesn't already exist. - labels...

(IF_NO_COMMA)


217-219: Use asterisk for emphasis and improve wording.

Switch to * for italics per markdownlint, and tighten phrasing for the note.

- _Note that zone name, latitude, longitude, and radius will be shared with Todoist in order to support the reminder._
+ *Note that zone name, latitude, longitude, and radius will be shared with Todoist to support location-based reminders.*
🧰 Tools
🪛 LanguageTool

[style] ~218-~218: Consider a more concise word here.
Context: ... and radius will be shared with Todoist in order to support the reminder._ - **reminder_lo...

(IN_ORDER_TO_PREMIUM)

🪛 markdownlint-cli2 (0.17.2)

218-218: Emphasis style
Expected: asterisk; Actual: underscore

(MD049, emphasis-style)


218-218: Emphasis style
Expected: asterisk; Actual: underscore

(MD049, emphasis-style)


228-229: Add explicit subject to reminder_location_direction note.

Start the sentence with a clear subject for completeness.

- Can only be set if `reminder_zone` or `reminder_location_name`, `reminder_latitude`, `reminder_longitude`, and `reminder_radius` are set.
+ This parameter can only be set if `reminder_zone` or `reminder_location_name`, `reminder_latitude`, `reminder_longitude`, and `reminder_radius` are set.
🧰 Tools
🪛 LanguageTool

[style] ~228-~228: To form a complete sentence, be sure to include a subject.
Context: ...sent when entering or leaving the zone. Can only be set if reminder_zone or `remi...

(MISSING_IT_THERE)


231-232: Clarify and correct grammar in reminder_users entry.

Fix possessive, streamline phrasing, and reorder for clarity.

- **reminder_users** (*Optional*): A list of member's usernames of a shared project to be reminded of this task. You find the possible usernames formatted as bold text in the collaborator menu of a shared project. If not specified, the user Home Assistant is authenticated as will be reminded.
+ **reminder_users** (*Optional*): A list of usernames of shared project members to be reminded of this task. You can find these usernames in bold within the collaborator menu of a shared project. If not specified, the authenticated Home Assistant user will be reminded.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~231-~231: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...eminder_users** (Optional): A list of member's usernames of a shared project to be r...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)


[uncategorized] ~231-~231: Possible missing comma found.
Context: ...t specified, the user Home Assistant is authenticated as will be reminded.

(AI_HYDRA_LEO_MISSING_COMMA)

📜 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 9419017 and 1433b4c.

📒 Files selected for processing (1)
  • source/_integrations/todoist.markdown (2 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/todoist.markdown

[uncategorized] ~193-~193: You might be missing the article “a” here.
Context: ...thin the project to add the task to. If section doesn't already exist it will be create...

(AI_EN_LECTOR_MISSING_DETERMINER_A)


[typographical] ~193-~193: It seems that a comma is missing.
Context: ...the task to. If section doesn't already exist it will be created (unless `create_sect...

(IF_COMMA)


[typographical] ~195-~195: Usually, there’s no comma before “if”.
Context: ... the specified section should be created, if it doesn't already exist. - labels...

(IF_NO_COMMA)


[style] ~218-~218: Consider a more concise word here.
Context: ... and radius will be shared with Todoist in order to support the reminder._ - **reminder_lo...

(IN_ORDER_TO_PREMIUM)


[style] ~228-~228: To form a complete sentence, be sure to include a subject.
Context: ...sent when entering or leaving the zone. Can only be set if reminder_zone or `remi...

(MISSING_IT_THERE)


[uncategorized] ~231-~231: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...eminder_users** (Optional): A list of member's usernames of a shared project to be r...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)


[uncategorized] ~231-~231: Possible missing comma found.
Context: ...t specified, the user Home Assistant is authenticated as will be reminded.

(AI_HYDRA_LEO_MISSING_COMMA)

🪛 markdownlint-cli2 (0.17.2)
source/_integrations/todoist.markdown

218-218: Emphasis style
Expected: asterisk; Actual: underscore

(MD049, emphasis-style)


218-218: Emphasis style
Expected: asterisk; Actual: underscore

(MD049, emphasis-style)

⏰ 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

* Create section if not exists
* Add location-based reminders
* Specify users to remind
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 (8)
source/_integrations/todoist.markdown (8)

193-193: Document default behavior for section creation.
The doc should state the default value of create_section (presumably true) when omitted to avoid confusion.


195-195: Specify default for create_section.
Clarify that create_section defaults to true if not explicitly set.


217-219: Clarify mutual exclusivity for reminder_zone.
Explicitly note that setting reminder_zone disables all coordinate-based parameters (reminder_location_name, reminder_latitude, reminder_longitude, reminder_radius) and vice versa.


220-221: Group coordinate-based reminder parameters.
Indicate that reminder_location_name must be used in tandem with reminder_latitude, reminder_longitude, and reminder_radius. Consider referencing them collectively to prevent partial configurations.


222-223: Merge latitude and longitude descriptions.
To reduce verbosity, consider combining reminder_latitude and reminder_longitude into a single “Location Coordinates” section or nested sub-items.


224-225: Specify units for reminder_radius.
Add the unit of measurement (e.g., meters) to ensure users understand the expected input.


228-229: Clarify reminder_location_direction requirements.
The description should state that reminder_location_direction is valid only when either reminder_zone or all coordinate-based parameters are provided. This avoids ambiguity over partial configurations.


231-231: Improve sentence clarity and fix missing comma.
Rephrase for readability and correct punctuation:

- If not specified, the user Home Assistant is authenticated as will be reminded.
+ If not specified, the authenticated Home Assistant user will be reminded.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~231-~231: Possible missing comma found.
Context: ...t specified, the user Home Assistant is authenticated as will be reminded.

(AI_HYDRA_LEO_MISSING_COMMA)

📜 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 1433b4c and e29795f.

📒 Files selected for processing (1)
  • source/_integrations/todoist.markdown (2 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/todoist.markdown

[uncategorized] ~231-~231: Possible missing comma found.
Context: ...t specified, the user Home Assistant is authenticated as will be reminded.

(AI_HYDRA_LEO_MISSING_COMMA)

⏰ 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 (1)
source/_integrations/todoist.markdown (1)

216-216: Skip blank line insertion.
This change appears to add a blank line; it doesn’t affect documentation content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has-parent This PR has a parent PR in a other repo in-progress This PR/Issue is currently being worked on next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant