Remove or guard /_test/* stub routes in production

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
api, backend

Research direction

Start at the three /api/_test/* route definitions added by the api-skeleton work in PR #17, then inspect the integration tests that exercise validation errors, internal errors, and idempotency replay. Decide whether removal or an environment guard fits the cutover plan; done means the test behavior remains available while production no longer exposes these routes.

Written by the indexing model from the issue text.

Description

The api-skeleton plan added three stub routes used only by integration tests:

  • POST /api/_test/validation-error — throws ApiValidationError for testing the error mapper
  • POST /api/_test/internal-error — throws a generic Error for testing 500 behavior
  • POST /api/_test/idempotency — tests idempotency key replay

These have { schema: { hide: true } } so they don't appear in the OpenAPI doc, but they're live in production. They should either be removed before cutover or guarded behind NODE_ENV !== 'production'.

Came out of api-skeleton (PR #17), Follow-up item.

Dominant language
TypeScript
Stars
1
Forks
1
Avg merge
1d 20h
Merged PRs (30d)
25

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 CodeForPhilly/codeforphilly-ng

All issues in CodeForPhilly/codeforphilly-ng

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.