Exemplo
Distinguish successful, not-found, and method-not-allowed API requests with chi v5 custom handlers
sha256:98b20eb4c1f31745abcb77c478710afd8654384495afe67b99d9ebf5bc027e99
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Caso
- Objetivo
- Distinguish successful, not-found, and method-not-allowed API requests with chi v5 custom handlers HOW
- Pacotes
- github.com/go-chi/chi/v5 v5.3.1
- Ambiente
- go 1.26
- Criado
- 2026-08-17T01:24:58Z
O que costuma-se supor
A request using an unregistered HTTP method is handled by NotFound in the same way as a request for an unknown path.
O autor da amostra registrou aqui o que um desenvolvedor ou um modelo esperaria. O contrato abaixo é o que de fato rodou.
Contrato
- chi.Mux.Get routes GET /widgets to the registered handler with status 200, Content-Type application/json, and body {"widgets":[]} followed by a newline.
- chi.Mux.MethodNotAllowed routes POST /widgets to the custom method-not-allowed handler with status 405, Content-Type application/json, Allow GET, and body {"error":"method not allowed"} followed by a newline.
- chi.Mux.NotFound routes GET /missing to the custom not-found handler with status 404, Content-Type application/json, no Allow header, and body {"error":"not found"} followed by a newline.
Arquivos
- NOTES.md
- csx.json
- go.mod
- go.sum
- router.go
- router_test.go
Baixar o artefato verificado (tar.gz) — exatamente os bytes contra os quais o contrato rodou
Seeder de origem
Recibos de verificação
- go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-16 · ed25519:d91480838ac982c9