refactor: use CoreToolCallStatus in the the history data model#19033
refactor: use CoreToolCallStatus in the the history data model#19033
CoreToolCallStatus in the the history data model#19033Conversation
CoreToolCallStatus in the the history data model
Summary of ChangesHello @jerop, 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 refactors the CLI's internal handling of tool call statuses. Instead of storing a simplified Highlights
Changelog
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 refactors the CLI to replace the UI-specific ToolCallStatus and various string literals with the centralized CoreToolCallStatus enum from @google/gemini-cli-core, updating the history data model, hooks, and components. This significantly improves type safety and aligns the CLI's internal state with the core library. A thorough security audit confirmed that no vulnerabilities were introduced, and existing security controls remain intact.
|
Size Change: +643 B (0%) Total Size: 24.4 MB ℹ️ View Unchanged
|
…allDisplay This refactor updates the CLI to store the high-fidelity 'CoreToolCallStatus' in the history data model (ToolCallEvent and IndividualToolCallDisplay) instead of the simplified 'ToolCallStatus'. The mapping to the display-oriented 'ToolCallStatus' is now deferred to the view layer (React components), ensuring that internal logic and hooks have access to the precise state of tool execution. Follow-up to #18998 Related to #18918
f353e4c to
9d91f8f
Compare

This refactor updates the CLI to store the high-fidelity
CoreToolCallStatusin the history data model (ToolCallEventandIndividualToolCallDisplay) instead of the simplifiedToolCallStatus.The mapping to the display-oriented
ToolCallStatusis now deferred to the view layer (React components), ensuring that internal logic and hooks have access to the precise state of tool execution.Follow-up to #18998
Related to #18918
Mapping from
CoreToolCallStatustoToolCallStatus:gemini-cli/packages/cli/src/ui/hooks/toolMapping.ts
Lines 22 to 44 in f460ab8