Skip to content

fix(tasks): warn when due time is ignored by API#700

Open
jeevan6996 wants to merge 1 commit intogoogleworkspace:mainfrom
jeevan6996:fix/696-tasks-due-time-warning
Open

fix(tasks): warn when due time is ignored by API#700
jeevan6996 wants to merge 1 commit intogoogleworkspace:mainfrom
jeevan6996:fix/696-tasks-due-time-warning

Conversation

@jeevan6996
Copy link
Copy Markdown

Summary

  • add a targeted warning when requests to Google Tasks include a non-midnight due timestamp, since the Tasks API stores only date information and discards time-of-day
  • scope the warning to Tasks write operations (POST/PUT/PATCH) so other APIs are unaffected
  • add unit tests for non-midnight detection, midnight-no-warning behavior, and non-Tasks API behavior
  • include a patch changeset

Fixes #696

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Apr 11, 2026

🦋 Changeset detected

Latest commit: e225662

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@googleworkspace/cli Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a proactive warning system for the Google Tasks CLI integration. By detecting when users provide a due date with a non-midnight time component, the CLI can now inform the user that this time information will be discarded by the Google Tasks API, thereby improving transparency and preventing potential confusion regarding task scheduling.

Highlights

  • Warning Implementation: Added a warning mechanism to alert users when a Google Tasks API request includes a non-midnight due timestamp, as the API ignores time-of-day information.
  • Scope Limitation: Ensured the warning is only triggered for Tasks write operations (POST, PUT, PATCH) to prevent false positives in other API calls.
  • Testing: Added comprehensive unit tests to verify the detection logic, ensuring midnight timestamps and non-Tasks APIs do not trigger the warning.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Generative AI Prohibited Use Policy, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces a warning for Google Tasks API requests that include a non-midnight due time, as the API only stores the date and ignores the time-of-day. The changes include a new utility to parse the due field and logic within the executor to print a warning to stderr during POST, PUT, or PATCH operations. A security concern was raised regarding the potential for terminal escape sequence injection because the warning message includes user-controlled input; a suggestion was provided to sanitize the output before printing.

let input = parse_and_validate_inputs(doc, method, params_json, body_json, upload.is_some())?;

if let Some(msg) = tasks_due_time_truncated_warning(doc, method, input.body.as_ref()) {
eprintln!("Warning: {msg}");
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

security-high high

The warning message includes the due value directly from the request body, which is user-controlled. To prevent terminal escape sequence injection, this string should be sanitized before being printed to the terminal. Note that Rust's char::is_control() only covers the Cc (Control) Unicode category, not Cf (Format), so is_dangerous_unicode is needed to check for dangerous Unicode characters.

Suggested change
eprintln!("Warning: {msg}");
eprintln!("Warning: {}", sanitize_for_terminal(&msg));
References
  1. Rust's char::is_control() only covers the Cc (Control) Unicode category, not Cf (Format). Therefore, is_dangerous_unicode is not redundant and is needed to check for dangerous Unicode characters.
  2. Sanitize error strings printed to the terminal to prevent escape sequence injection.

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.

Bug - Tasks - set due time

2 participants