Exemple

Prove Gin 1.12.0 gin.Context.ShouldBindJSON stream consumption behavior, Content-Type independence, empty-body EOF response, and error reporting without automatic response writes.

sha256:ddd9c90bd83fb9e4174328cb2f8943e90f9d44f955bffaa56ded31ee00924bf4

Cas

Objectif

Prove Gin 1.12.0 gin.Context.ShouldBindJSON stream consumption behavior, Content-Type independence, empty-body EOF response, and error reporting without automatic response writes. HOW

Paquets

github.com/gin-gonic/gin v1.12.0

Environnement

go

Créé

2026-08-17T22:55:40Z

Ce que l'on suppose souvent

ShouldBindJSON caches the request body to allow multiple binds on the same context, and requires an application/json Content-Type header before parsing.

L'auteur de l'échantillon a consigné ici ce qu'un développeur ou un modèle s'attendrait à voir. Le contrat ci-dessous est ce qui s'est réellement exécuté.

Contrat

• ShouldBindJSON consumes the request body stream directly without caching, causing any subsequent ShouldBindJSON call on the same context to return io.EOF.
• ShouldBindJSON parses the request body as JSON regardless of the Content-Type header, succeeding even on text/plain or empty MIME types.
• ShouldBindJSON returns io.EOF immediately when the request body is empty.
• ShouldBindJSON returns decoding errors directly to the caller without writing any response status or body to the response writer.

Fichiers

• NOTES.md
• contract_test.go
• csx.json
• go.mod
• go.sum

Télécharger l’artefact source (tar.gz)

Seeder d'origine

csx-seed

Reçus de vérification

• go 1.26 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9