[11/44] Enable TS strict mode in utils-testing
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Part of the strict-mode rollout epic #35932. Enable TypeScript strict mode for the utils-testing project using typescript-strict-plugin.
- Dependency layer: 2 (0 = leaf library, 10 = top-level app)
- Internal dependents: 18 project(s)
- Rollout order: 11 / 44
- Note: Test utilities - improves typing of specs across the repo.
All internal dependencies of utils-testing should already be in strict mode before starting (they appear earlier in the rollout order).
Acceptance Criteria
-
utils-testing'ssrcis added to thetypescript-strict-pluginstrictpathsconfig. - All resulting type errors are resolved (no new
any; use explicit types). -
// @ts-strict-ignoreis used only where unavoidable, each with a follow-up TODO. -
yarn nx run utils-testing:lintpasses (and:build/:testwhere applicable). -
npx tsc-strictpasses forutils-testing. -
yarn nx affected -t builddoes not break dependents.
Priority
Medium
Additional Context
One project in the bottom-up rollout tracked by epic #35932. Depends on the bootstrap task being merged and on lower-layer projects already being strict.
Contributor guide
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 the strict-mode rollout epic #35932 and the utils-testing project configuration, then add utils-testing/src to the typescript-strict-plugin strict paths. Run npx tsc-strict and resolve the resulting errors with explicit types, using // @ts-strict-ignore only with follow-up TODOs. Verify with the project's lint, build, test, and affected-build commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100