anomalyco / anomalyco/opencode-drive
test: type-check Drive test sources
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 32
- Forks
- 3
- Avg merge
- 12m
- Merged PRs (30d)
- 17
Description
Problem
packages/drive/tsconfig.json checks src, examples, compile fixtures, and manual probes, but excludes ordinary test/**/*.test.ts and test/fixtures/**. Vitest strips types, so test API drift can stay invisible until a line happens to fail at runtime.
A diagnostic config including the full test tree currently reports roughly 50 errors. Examples include stale Effect APIs, unchecked indexed access, scope requirements, overly broad error unions, and fixture contract drift.
Proposed sequence
- Add
tsconfig.test.jsonand atypecheck:testscript, but keep it out of required CI initially. - Fix errors in small file-scoped commits, starting with:
test/driver/index.test.tstest/tool/producer.test.tstest/instance/proxy.test.tstest/tool/controller.test.tstest/fixtures/**
- Add
typecheck:testtocheckonce the diagnostic config is clean.
Done when
- Production and test TypeScript checks both pass.
- Script fixtures are covered, since
start --scriptcompiles them as user programs. - Runtime test behavior and assertions remain unchanged.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with packages/drive/tsconfig.json and the existing scripts, then inspect the reported errors in test/driver/index.test.ts, test/tool/producer.test.ts, test/instance/proxy.test.ts, test/tool/controller.test.ts, and test/fixtures/**. Add the diagnostic test configuration and script, resolve the file-scoped type errors, and confirm production and test checks pass without changing runtime assertions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, testing, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100