arrow_backRetour aux issues
Xconfess/Xconfess
#1718
Débutant
Ouvrirarrow_forward
Débutant
Ouvrirarrow_forward
Débutant
Ouvrirarrow_forward
frontend: standardize method-not-allowed responses across proxy routes
ecoDébutant
help wanted
Frontend
Stellar Wave
api
Maybe Rewarded
tests
P2
descriptionDescription
## Problem
Only some Next.js proxy routes return a consistent JSON 405 response with an Allow header.
## Scope
- Reuse `methodNotAllowed` from `app/lib/api/proxy.ts` across high-traffic API routes.
- Start with auth, users, confessions, comments, and notifications routes.
## Acceptance criteria
- Unsupported methods return `{ code: METHOD_NOT_ALLOWED }`.
- Responses include an `Allow` header.
- Add focused route tests for at least two routes.
## Validation
Run:
`npm run test --workspace=xconfess-frontend -- app/api --runInBand`
Issues similaires
lingdojo/kana-dojo
star3.2k
Poids du dépôt lourd
[Good First Issue] 🐡 Add new Japan Fact 251 - Beginner-Friendly Open-source Contribution
## 🟢 Good First Issue: Add Japan Fact #251 — Beginner-Friendly Open Source Contribution ![Time: <1 minute](https://img…
TypeScript
enhancement
help wanted
WasiqB/multiple-cucumber-html-reporter
star281
Poids du dépôt moyen
Error bucketing
It would be great to bucket the errors in different types i.e. Code exception, configuration exception, environmental e…
TypeScript
enhancement
help wanted
StellarLock/StellarLock
star0
Poids du dépôt léger
LP lock links omit the /token|lp/ URL segment, causing wrong-type lookups on the detail page
## Summary Lock detail links should include the lock's kind in the URL, e.g. `/app/lock/lp/:id` or `/app/lock/token/:i…
TypeScript
bug
good first issue