Expose a CLI tools management UI (Settings → CLI Tools)

Abierto
  • ¿Algo no está bien?
#39 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
54/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
react, rust, tauri, typescript
Área
database, desktop, frontend

Línea de trabajo

Start with src/components/ui/SettingsDialog and inspect src/components/ui/CliDownloadDialog.tsx and src/store/cliStore.ts to understand the existing download flow and available commands. Build a Settings → CLI Tools management surface for supported database tools, covering cached and PATH versions, downloads, and removal while retaining the inline fallback. Done when users can manage those tools from Settings and the download flow can be exercised there.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

CLI tool downloads (psql, mysql, etc.) currently fire inline during the first query in a psql console session: the user clicks Run, gets a "Download psql 16 (~80MB)?" confirm dialog, waits for the download, and only then sees their query execute. This is jarring UX — particularly because the download is large and connection-blocking.

Proposal

Add a Settings → CLI Tools section (or top-level Tools entrypoint) that lets users:

  • See which CLI tools are cached, with version + install path + size
  • See which versions are detected on the system PATH
  • Pre-download any version of any supported tool kind on demand
  • Remove a cached tool to free disk space

The inline download confirm during query execution stays as a fallback for users who skip the management UI.

What's already in place

Most of the infrastructure exists:

  • `src-tauri/src/cli.rs` already exposes `cli_check_tools`, `cli_list_cached`, `cli_check_tool`, `cli_check_system_tool`, `cli_download_version` Tauri commands.
  • `src/store/cliStore.ts` wraps them as a Zustand store.
  • `src/components/ui/CliDownloadDialog.tsx` is a fully-functional download dialog — but it isn't imported or rendered anywhere. Grep confirms zero call sites.

So the work is roughly: design the management surface, render it inside SettingsDialog (or a new modal), and either reuse `CliDownloadDialog` or fold its logic into the new view.

Additional benefit (testing)

This UI would let contributors force a download in QA scenarios — currently the only way to exercise `reqwest`'s HTTPS path is through the psql console flow, which silently skips the download when a matching system install is on PATH. See PR #37 smoke notes.

Out of scope

  • Choosing a default tool version per connection (existing connection settings already handle this).
  • Managing non-DB tools (psql/mysql/etc. only — same scope as the current `ToolKind` enum in `cli.rs`).
Lenguaje dominante
TypeScript
Estrellas
6
Forks
1
Merge medio
17 min
PR fusionados (30 d)
2

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de openidle-dev/queryden

Todos los issues de openidle-dev/queryden

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.