You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we have diverged significantly from what encoding/json supports, it seems like it could be more confusing than helpful to support the json:"" tag.
A couple of examples of dissonance:
We use lowerCamelCase for untagged fields, whereas the stdlib uses the literal Go field name casing.
We support encoding/decoding sum types, Go does not at all.
The text was updated successfully, but these errors were encountered:
safeer
added
next
Work that will be be picked up next
and removed
triage
Issue needs triaging
next
Work that will be be picked up next
labels
Jun 17, 2024
Now that we have diverged significantly from what
encoding/json
supports, it seems like it could be more confusing than helpful to support thejson:""
tag.A couple of examples of dissonance:
lowerCamelCase
for untagged fields, whereas the stdlib uses the literal Go field name casing.The text was updated successfully, but these errors were encountered: