text: reject unknown fields by default - #371
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
|
[claude code] Thanks for this. The direction matches upstream, and I'd like to take it for the next release with a bold changelog line, but CI's conformance job shows a contract the strict default breaks: 40 The fix belongs in codegen: the message descriptor carries Two smaller things while you're in there: the changelog fragment should say explicitly that reserved names are still skipped, and please keep |
|
@iainmcgin Thanks, let me fix this one. |
88876f1 to
c3d71e6
Compare
What changed
UnknownFieldfor unknown field names.Anyparser, and empty messages use the same strict behavior.Why
user_nmaewas previously ignored.TextFormatimplementations can still callskip_value()when lenient parsing is wanted.Checks
task linttask doctask test