check: explain how to validate one-shot Effect programs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
Start with the README's one-shot Effect example and reproduce the failure using opencode-drive check drive.ts. Compare the check path with opencode-drive run, which successfully typechecks this program shape. Done means the supported shape validates or the command gives clear guidance to use run or defineScript instead of exposing an internal TypeScript contract error.
Written by the indexing model from the issue text.
Description
With Drive 2.1.0, opencode-drive check drive.ts on a default-exported OpenCodeDriver.use(...) program reports TS2322: Type Effect<...> is not assignable to type ScriptDefinition from the generated script-contract file. The program shape is supported by opencode-drive run but the error does not explain the distinction.
Reproduction: save the README's one-shot Effect example and run opencode-drive check against it. Expected: validate the supported one-shot shape, or explain that check accepts defineScript and direct the caller to run. Actual: an internal TypeScript contract error.
This came up while preparing a matched TUI recording against OpenCode V2 revision 7a4ad68af6. Recovery is to use run, which performs its own typecheck.
- Dominant language
- TypeScript
- Stars
- 32
- Forks
- 4
- Avg merge
- 10m
- Merged PRs (30d)
- 13
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from anomalyco/opencode-drive
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anomalyco/opencode-drive#102 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
anomalyco/opencode-drive#104 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
anomalyco/opencode-drive#103 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
anomalyco/opencode-drive#97 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 52/100
anomalyco/opencode-drive#85 ·
Maintainers usually reply within 1 day
All issues in anomalyco/opencode-drive
Similar issues
-
priority: P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
prime-radiant-inc/evener#3291 ·
Maintainers usually reply within 1 day
-
accessibility bug revealjs
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
quarto-dev/quarto-cli#14961 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
supabase/agent-skills#614 ·
-
Content
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
RunestoneInteractive/rs#1559 · 1 comment ·
Maintainers usually reply within 2 days