-
Notifications
You must be signed in to change notification settings - Fork 0
cleanup opportunities
The source tree has no TODO, FIXME, or HACK comments in the scanned application, backend, scripts, and docs paths. The opportunities below are structural follow-ups from file size, duplicated contract surfaces, and release workflow shape.
| File | Lines | Why it matters |
|---|---|---|
src-tauri/src/k6/process/runtime.rs |
1,738 | Binary lookup, process launch, output forwarding, fallback diagnostics, and artifact cleanup share one file |
src-tauri/src/k6/tests.rs |
1,656 | Broad k6 runtime test coverage could be split by behavior |
src/styles/app.css |
1,404 | All app styling is centralized |
src-tauri/src/importing/tests.rs |
1,034 | Import parsing test cases are grouped in one file |
TypeScript and Rust models are manually mirrored in src/lib/loadrift/types.ts and src-tauri/src/models.rs. The same is true for command/event names across src/lib/loadrift/api.ts, src/lib/tauri/client.ts, and src-tauri/src/events.rs. Generated bindings or schema checks could catch drift earlier.
.github/workflows/release.yml contains a large inline shell section for APT repository signing, setup package validation, signature verification, and Pages deployment. scripts/build_apt_repository.py already holds repository generation logic, so more validation code could move into scripts if the workflow grows.
src-tauri/src/k6/process/runtime.rs includes a Windows target triple for k6 lookup, while scripts/install-k6.sh, .github/workflows/release.yml, and README.md focus on Linux and macOS. A future Windows release path should either be implemented fully or documented as unsupported.
For current codebase size data, see By the numbers.