anomalyco / anomalyco/opencode-drive

test: type-check Drive test sources

Open
#97 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
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

  1. Add tsconfig.test.json and a typecheck:test script, but keep it out of required CI initially.
  2. Fix errors in small file-scoped commits, starting with:
    • test/driver/index.test.ts
    • test/tool/producer.test.ts
    • test/instance/proxy.test.ts
    • test/tool/controller.test.ts
    • test/fixtures/**
  3. Add typecheck:test to check once the diagnostic config is clean.

Done when

  • Production and test TypeScript checks both pass.
  • Script fixtures are covered, since start --script compiles them as user programs.
  • Runtime test behavior and assertions remain unchanged.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.