zeekayandHanzo Dev cb7c5fb64c The name is checked against what the encoder does ...

The wire is stated in three places that have to agree: the option set, the
constant's value, and the comment explaining it. The existing cases fail the
moment the options move — and would pass happily while the name went on
claiming semantics the encoder no longer has, which is the one an operator
reads in a startup line.

So the name is now asserted against the bytes: it may say "sorted keys" exactly
when a map comes out sorted, and "v1 semantics" exactly when a zero under
omitempty is left out. It fails in both directions — options moved, or name
moved — and says which disagreed.

Co-authored-by: Hanzo Dev <[email protected]>

2026-09-17 06:03:14 -07:00

..

doc.go

The wire is stated, and the encoder is v2

2026-09-17 01:19:25 -07:00

jsonenc_test.go

The name is checked against what the encoder does

2026-09-17 06:03:14 -07:00

jsonenc.go

The encoder's name says what it writes

2026-09-17 05:59:33 -07:00