test(core): add regression test for issue for ToolConfirmationResponse#26194
test(core): add regression test for issue for ToolConfirmationResponse#26194
Conversation
Summary of ChangesHello, 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 regression test to ensure the stability of the ToolConfirmationResponse handling logic. By validating that the payload parameter is correctly propagated to the onConfirm callback, this change prevents future regressions related to issue #22120. Highlights
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. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request adds a regression test in packages/core/src/scheduler/confirmation.test.ts for issue #22120. The test ensures that the payload from a tool confirmation response is correctly passed to the onConfirm callback. I have no feedback to provide.
|
Size Change: -4 B (0%) Total Size: 33.9 MB
ℹ️ View Unchanged
|
Summary
Adds a regression test to ensure that the
payloadfrom aToolConfirmationResponseis correctly passed to theonConfirmcallback.Details
Issue #22120 reported that
CoreToolScheduler.handleConfirmationResponsewas dropping thepayloadparameter. This bug was fixed during the migration to the new event-driven scheduler (specifically inpackages/core/src/scheduler/confirmation.ts), where the payload is correctly retrieved from the response message and passed to the callback.This PR adds a dedicated unit test in
packages/core/src/scheduler/confirmation.test.tsto verify this behavior and prevent regressions.Related Issues
Fixes #22120
How to Validate
Run the unit tests for the core package:
npm test -w @google/gemini-cli-core -- src/scheduler/confirmation.test.tsThe new test case "should pass payload to onConfirm callback (Regression for #22120)" should pass.
Pre-Merge Checklist