Add support for HTTP 405 (Method Not Allowed)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Worktop returns a [404 Not Found](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405) instead of a [405 Method Not Allowed](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405) for an invalid method on a valid resource. This can cause developers to lose time debugging errors as they look for a missing resource definition rather than an incorrect method, which can happen easily when copy/pasting routes.
Contributor guide
No contributing guide indexed for this repository
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 by tracing Worktop's route matching and method handling entry points to distinguish an invalid method on a valid resource from a missing resource. Confirm the current 404 behavior, then verify that the invalid-method case returns HTTP 405 while genuinely missing resources remain 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100