Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[test-debt] Make Worker recovery fixture inputs type-correct in a focused test-inclusive check

Open Beginner friendly
  • Is something wrong?
#539 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
testing

Research direction

Start with apps/nanocore/src/runtime/worker-control-rebuild.test.ts and inspect the recovery fixture inputs and their declared types. Check the repository's actual test execution model and configure a focused test-inclusive type check without weakening compiler settings or adding a runner. Keep runtime values, assertions, mismatch cases, authority, and bounds unchanged; done when the three existing cases pass and the focused check reports no fixture input errors.

Written by the indexing model from the issue text.

Description

The recovery fixture in apps/nanocore/src/runtime/worker-control-rebuild.test.ts has two existing test-input type errors under an explicit test-inclusive check. The normal NanoCore package typecheck excludes *.test.ts, so its passing result does not cover these inputs.

At e7d427a63b9e59b112473a734665c430b910b6c6, the retained R3483 comparison found the same diagnostics on parent and candidate:

  • TS2379: the scheduler admission input includes an optional requestId value that can be undefined, while CreateSchedulerAdmissionEntryInput permits omission or string | null.
  • TS2345: the mismatch table widens an actor's kind to string instead of retaining its closed literal type.

Correct these fixture input types without changing their runtime values, assertions, mismatch cases, authority or bounds. Verify the existing three cases and a correctly configured focused test-inclusive check. Do not add a new test runner or weaken compiler settings.

The comparison also reported TS1470 under its NodeNext probe configuration. Treat that as an instrument/module-configuration question until checked against the repository's actual test execution model; it is not proof that the production ESM build is broken. The initial missing Node type-root probe was invalid and is not credited.

This debt predates the native source-root fixture correction; the candidate added no diagnostic. That limits attribution, but does not close the debt. Related program index: #374.

Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
3h 54m
Merged PRs (30d)
5

Getting set up

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.

More from lingkaix/openkit

All issues in lingkaix/openkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.