#523 - TypeScript hardening for runtime-critical path

Open
#529 0 comments 0 reactions 1 assignee View on GitHub

@brijesh-amin is already working on this.

Since Jul 17, 2026.

Assessment

This issue has not been assessed yet.

Description

Parent: #523

Objective

Increase type safety where failures are most costly by removing @ts-nocheck and tightening types in bootstrap/router/auth entry paths.

In scope

  • Prioritize: src/index.ts, src/router/index.ts, src/libs/authmware.ts (and directly related helpers)
  • Remove @ts-nocheck in targeted files
  • Add/adjust types for request context, auth payloads, and shared utilities

Acceptance criteria

  • Target files compile without @ts-nocheck
  • No behavior regressions in auth + route bootstrap
  • Unit/integration tests pass for touched paths
  • New/changed code avoids broad any where practical

Notes

Work in small PRs to keep review manageable.

Dominant language
TypeScript
Stars
1
Forks
7
No merged PRs in 30d

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.

More from bcgov/range-api

All issues in bcgov/range-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.