tmu
9a08262076
Record the decision to host CI coverage from a tiny dir-listing server in the Gitea docker setup (shared volume keyed by repo/tag) instead of the GitHub upload-artifact zip. This unblocks dropping the coverage artifact from the Gitea CI port. Adds the lipanski docker-image author to cspell.
60 lines
3.4 KiB
Plaintext
60 lines
3.4 KiB
Plaintext
Tasks
|
|
|
|
Backlog and tracking for tiny-pattern-ts. Managed in vscode-todotasks format.
|
|
|
|
---
|
|
|
|
Setup:
|
|
☐ Establish release CI workflow: post-tag checks + npm publish after release tag push => pi --session 01a06e72-e61e-7327-b3e9-3e11749a523f @high
|
|
☐ Add gitea release page in CI @high
|
|
☐ Split off template into separate package => pi --session 01a07dde-7050-7054-bb36-1606d7eb2bc3 @high
|
|
✔ Document branching model @done
|
|
✔ Describe branching model: when to branch, base branch, naming @done
|
|
✔ Clarify release workflow: who pushes `main`, CI as post-merge gate, drop PR usage @done (9/8/2026, 2:54:32 PM)
|
|
✔ Evaluate connecting the agent to lsp typescript server @done
|
|
- might be more difficult with TS7, since LSP Server has changed from 6
|
|
- but since vscode is running TS7, maybe it is possible to connect to the TS7 LSP server of vscode
|
|
- LSP servers in general?
|
|
- maybe skills?
|
|
→ resolved: adopted @spences10/pi-lsp@0.0.46 as a project-local pi extension (`.pi/settings.json`). It auto-detects the repo's TypeScript 7 (no `lib/tsserver.js`) and spawns `tsc --lsp --stdio` — the same tsgo binary VS Code's native-preview uses. Read-only: hover / definition / references / symbols / diagnostics. No skill; skills don't own persistent processes.
|
|
|
|
✔ Adopt a `setup:` prefix for one-time clone configuration @done
|
|
✔ Register `use:git-commit-message` as its first member (and retire `use:` — it is in no prefix list) @done
|
|
✔ Create an umbrella 'setup' task that runs all setup tasks - currently one @done
|
|
|
|
v1.0:
|
|
☐ API surface is stable and fully typed
|
|
☐ Finalize public exports in `src/index.ts`
|
|
☐ Document all exported types and functions
|
|
☐ Add JSDoc for public APIs
|
|
☐ Test coverage meets threshold
|
|
☐ Achieve 100% branch coverage on `src/pattern.ts`
|
|
☐ Achieve 100% branch coverage on `src/match.ts`
|
|
☐ Achieve 100% branch coverage on `src/index.ts`
|
|
☐ `dist/` output is clean
|
|
☐ Verify `.d.ts` declarations match public exports
|
|
☐ Ensure `.js` files use `.js` extensions (not `.ts`)
|
|
☐ Test `attw --profile esm-only` passes
|
|
|
|
Bugs:
|
|
|
|
Enhancements:
|
|
|
|
Documentation:
|
|
☐ Add usage examples to README.md
|
|
☐ Create `examples/` directory with runnable snippets
|
|
☐ Add comparison section vs. other TS pattern-matching libs
|
|
☐ Write migration guide for users coming from discriminated unions
|
|
☐ Create backlog tasks for implementation
|
|
|
|
Maintenance:
|
|
☐ Serve CI coverage over a tiny self-hosted webserver (replace the zip artifact) @low
|
|
☐ Add a minimal dir-listing webserver to the gitea docker setup (e.g. caddy `file_server browse` reusing the existing reverse proxy, or any single-binary static server, lipanski/docker-static-website)
|
|
☐ CI writes each run's `coverage/` into a shared volume keyed by project + tag (e.g. `/coverage/tiny-pattern-ts/<tag>/`)
|
|
☐ Browse to `…/coverage/<repo>/<tag>/index.html` in the browser; drop the `actions/upload-artifact` coverage step in favour of the shared-dir layout
|
|
→ design: no deploy step in CI; the webserver just exposes the shared directory (decided over Gitea Pages / Codecov — neither confirmed available/ wanted)
|
|
✔ Set up lefthook pre-commit hook @done (9/8/2026, 10:52:56 AM)
|
|
✔ Configure tsconfig strictest + node26 profiles @done (9/8/2026, 10:08:37 AM)
|
|
✔ Add check:tsc as first tier in `npm run check` @done (9/8/2026, 10:08:37 AM)
|
|
✔ Pin Node.js >= 26 via `.node-version` @done (9/8/2026, 10:08:38 AM)
|