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

未关闭
#39 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
54/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
react, rust, tauri, typescript

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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`).
主要语言
TypeScript
星标
6
派生
1
平均合并
17 分钟
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

openidle-dev/queryden 的其他 Issue

查看 openidle-dev/queryden 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。