Tab Completion

TypeScript `src/routes/invoices.ts` cursor is inside `async (req, res) => {` after `try {`. Tab offers a single-line `res.json({ ok: true });` ghost text but the handler must validate `req.params.id`, call `billingService.charge`…

Tab suggests a multi-line block covering validation, service call, and catch with `res.status(400|500).json({ error })` matching project patterns; user can Tab-accept full block or partial-accept line-by-line.

File `crates/api/src/handlers/user.rs` already imports `crate::db::DbError` and `User`. Cursor on `match fetch_user(id).await {` with no arm yet. Tab should propose `Ok(user) =>` and `Err(e) =>` arms consistent with Axum `IntoRes…

Completion uses existing imports, does not duplicate `use` lines, and proposes `Err(e)` mapping consistent with neighboring handlers (e.g., `AppError::from(e)`).

Python `services/parser.py` — Tab suggests full `def parse_config(path: str) -> Config:` plus docstring and body. Operator wants signature + type hints only, then will write validation manually.

Partial accept (word/line accept per Tab docs) applies only through the signature line; remaining ghost text stays available or dismisses without inserting full body.