Conversation
This field is not present in the TypeScript `ComputedTask` definition and was identified for removal. This commit removes: - The `is_blocked` field from the `ComputedTask` struct in `crates/tasklens-core/src/types/transient.rs`. - The assignment of `is_blocked` in `crates/tasklens-core/src/domain/priority.rs`. - The `is_blocked` field from `ExpectedTaskProps` and the corresponding assertion in `crates/tasklens-core/tests/compliance.rs`. - The reference to `is_blocked` in `docs/design/test-suite.md`. All tests in `tasklens-core` pass. Co-authored-by: matta <37314+matta@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Merging to
|
Summary of ChangesHello @matta, 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 streamlines the core Highlights
Changelog
Activity
Using Gemini Code AssistThe 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
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 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. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request correctly removes the is_blocked field from the ComputedTask struct, which is no longer needed. The change is consistently applied across the domain logic, tests, and documentation, simplifying the data model and aligning it with the TypeScript implementation. I've found one minor issue regarding a leftover comment that should be addressed to maintain code clarity.
I am having trouble creating individual review comments. Click here to see my feedback.
crates/tasklens-core/src/types/transient.rs (122-123)
There appears to be an off-by-one error in the lines removed. You've removed is_blocked (line 122) and the TODO comment for is_visible (line 123). This leaves the TODO comment from is_blocked (line 121) incorrectly pointing to is_visible.
The correct change would be to remove is_blocked and its own TODO comment, which are on lines 121 and 122.
|
Waiting on the result of #480 |
Understood. I will wait for the result of that PR. |
This field is not present in the TypeScript `ComputedTask` definition and was identified for removal. This commit removes: - The `is_blocked` field from the `ComputedTask` struct in `crates/tasklens-core/src/types/transient.rs`. - The assignment of `is_blocked` in `crates/tasklens-core/src/domain/priority.rs`. - The `is_blocked` field from `ExpectedTaskProps` and the corresponding assertion in `crates/tasklens-core/tests/compliance.rs`. - The reference to `is_blocked` in `docs/design/test-suite.md`. All tests in `tasklens-core` pass. Co-authored-by: matta <37314+matta@users.noreply.github.com>
Removed
is_blockedfield fromComputedTaskstruct and related assignment inpriority.rs, as well as updated tests and documentation.PR created automatically by Jules for task 11144978107209981231 started by @matta