Files
BoosAPI/desktop/libs/stream-monaco/todo.md
T
boos e0a5f57793 feat(desktop): embed BoosAPI Desktop client as a subproject
Vendor the rebranded BoosAPI Desktop client (Tauri + Vue) into metapi as
a monorepo subdirectory under desktop/. Source only — node_modules,
dist, Cargo target and the upstream .git history are excluded.

desktop/ keeps its own independent Cargo workspace (desktop/src-tauri
with crates/*); it is not part of the backend boosapi crate, so a
`cargo check` at the metapi root still compiles only the backend. Build
the desktop app from desktop/src-tauri per desktop/README.md.

Note: app icons are still placeholder assets pending the final BoosAPI
logo. The updater signing keys live outside the repo and are not
included.
2026-06-22 11:32:57 +08:00

1.5 KiB

TODO

Current Focus

  • Keep shrinking src/core/DiffEditorManager.ts only where the next slice is low-coupling and behavior-preserving.
  • Extract unchanged-region reveal button wiring and bridge wheel handling into helpers.
  • Extract the remaining center activation / click-flow glue into helpers if it can stay stateless.
  • Re-evaluate the unchanged-region area after each slice and stop once the remaining code is mostly orchestration.

Validation Plan

  • Run pnpm lint.
  • Run pnpm typecheck.
  • Run targeted unchanged-region presentation tests first.
  • Run the full pnpm vitest run suite after each landed slice.

Remaining Follow-ups

  • Decide whether DiffEditorManager should stop here or split one level further by responsibility.
  • Keep src/index.base.ts as orchestration only and avoid reintroducing editor update logic there.
  • If a future unchanged-region feature touches this area again, prefer another stateless DOM/helper slice before growing DiffEditorManager in place.
  • Audit clearHighlighterCache() semantics against the other shared highlighter state.
  • Align README.md, package.json, CHANGELOG.md, and release workflow version story.
  • Add at least one Playwright smoke job to CI.
  • Add at least one real framework example (React or Vue) to match the package positioning.
  • Verify package side-effect metadata against the automatic worker hook behavior.
  • Verify the build target / platform choices and document the reason if they stay as-is.