joaoh82 / rust_sqlite / 25205852918

69%

Build Type

push

github

Committed by web-flow

Commit Message

Phase 7g.3: Desktop "Ask…" button (#62)

Adds a natural-language → SQL composer to the Tauri desktop app's
query editor. Click "Ask…", type a question (e.g. "How many users
are over 30?"), submit, generated SQL drops into the editor textarea
for the user to review + Run themselves. Same engine surface the
REPL's `.ask` command uses (Phase 7g.2), with a Tauri command bridge.

## UX

The composer is a slide-in panel above the editor surface, opened
by an "Ask…" button on the editor toolbar (sits next to "Run" with
a subtle accent so it reads as a new feature without shouting).
Inside the panel: a question textarea, a "Generate SQL" button, an
explanation slot, and a close button. Cmd/Ctrl+Enter submits; Esc
closes.

  * Generated SQL replaces the editor contents — does NOT auto-run.
    The user reviews and clicks Run when they're ready. Matches the
    REPL's "confirm-and-run" UX one layer up.
  * The model's one-sentence rationale shows in the explanation slot
    (helpful for sanity-checking the generated query).
  * Empty SQL response — when the model decides the schema can't
    answer the question — surfaces the model's explanation in the
    same slot rather than silently doing nothing or erasing the
    editor.
  * Errors (missing API key, network failure, API error) land in the
    existing error slot.
  * On successful generation, focus moves back to the editor textarea
    so Cmd/Ctrl+Enter just runs.

## Backend (`ask_sql` Tauri command, ~30 LOC)

  * Reads `AskConfig::from_env()` — `SQLRITE_LLM_API_KEY` etc.
    Tauri inherits the parent shell's env on launch.
  * Locks the app's `Database` (so the schema dump is consistent
    with what the user would see if they ran `.tables`).
  * Calls `sqlrite::ask::ask_with_database` — schema introspection +
    cache-friendly prompt + sync HTTP POST happen entirely in the
    Rust backend.
  * **The API key never crosses into the webview.** That's the
    security story — same reasoning as Q9's WASM ... (continued)

Coverage Stats

0 of 6 new or added lines in 1 file covered. (0.0%)

484 existing lines in 1 file now uncovered.

5496 of 9331 relevant lines covered (58.9%)

1.21 hits per line