google-gemini/gemini-cli

Fix unsafe type assertions (Refactoring Plan)

Chiusa

#19.708 aperta il 20 feb 2026

Vedi su GitHubGuida contributor
 (18 commenti) (0 reazioni) (1 assegnatario)TypeScript (13.657 fork)batch import
area/coreeffort/largehelp wantedkind/bugpriority/p2status/bot-triaged

Metriche repository

Star
 (103.992 stelle)
Metriche merge PR
 (Merge medio 4g 2h) (55 PR mergiate in 30 g)

Descrizione

Tracking issue for removing no-unsafe-type-assertion suppressions introduced in PR #18688.

The goal is to replace as Type casts with runtime validation (Zod, instanceof, type guards).

This is a meta-issue to track the progress of the following sub-tasks.

  • #19709 - Phase 1.1: Error Handling (Core Utilities)
  • #19710 - Phase 1.2: JSON & Config (Core Utilities)
  • #19711 - Phase 2.1: Tool Execution (Core Tools)
  • #19712 - Phase 2.2: File System (Core File System)
  • #19713 - Phase 3.1: CLI Config
  • #19714 - Phase 3.2: CLI Activity Logger
  • #19715 - Phase 4.1: A2A Server
  • #19717 - Phase 4.2: VS Code Companion (Likely empty/already done)
  • #19733 - Phase 5: CLI Commands
  • #19734 - Phase 6: CLI UI
  • #19735 - Phase 7: Core MCP & Code Assist

Guida contributor

Direzione di ricerca
This is a meta issue tracking the removal of unsafe type assertions in the Gemini CLI codebase. The issue lists several subtasks (e.g., #19733, #19734, #19735) that are still open. Each subtask involves replacing `as Type` casts with runtime validation using Zod, type guards, or instanceof. To contribute, first review the existing refactoring pattern from completed subtasks (e.g., #19709–#19714) by examining their pull requests. Then choose an open subtask, ensure no one is assigned, and implement the changes in the relevant files (likely under `src/`). The maintainers have provided guidance in comments; read through the discussion to understand acceptance criteria.
Tech stack
typescriptnodejs
Dominio
backendtoolingdeveloper experience
Tipo issue
Refactoring
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
Oltre 1 settimana
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
Attiva
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
Richiede indagine
Prerequisiti
TypeScriptZod or similar validation library
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
20