0c9f0a9c5d
The wire representation of the contents of an Any is a `bytes` field containing the the wire encoding of the contained message. The in-memory representation is just these bytes. The wire (un)marshaler has no special handling for Any values, and happily accepts whatever bytes are present. The text and JSON marshalers will unmarshal the bytes in an Any, and the unmarshalers will marshal the Any to produce the in-memory representation. This makes them stricter than the wire (un)marshaler: Marshaling an Any which contains invalid data to text/JSON fails, while marshaling it to wire format does not. This does make some sense, since the Any already contains wire-format data; validation is performed at an earlier time when producing that data. This change brings the text and JSON (un)marshal functions a bit more into alignment with the wire format by never performing checks for required fields on the contents of an Any. This has the advantage of consistently performing checks for required fields exactly once per marshal/unmarshal operation, and over the same data no matter which encoding is used. It also eliminates the one case where a required field check is considered "non-fatal", generating an error but not terminating the (un)marshal operation. Change-Id: I70c62419d37ea0a07cb73c3ee2d26c0b0bec724b Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/182982 Reviewed-by: Herbie Ong <herbie@google.com> |
||
|---|---|---|
| cmd | ||
| compiler/protogen | ||
| encoding | ||
| internal | ||
| proto | ||
| reflect | ||
| runtime | ||
| testing/prototest | ||
| types | ||
| .gitignore | ||
| .travis.yml | ||
| AUTHORS | ||
| CONTRIBUTING.md | ||
| CONTRIBUTORS | ||
| go.mod | ||
| go.sum | ||
| integration_test.go | ||
| LICENSE | ||
| PATENTS | ||
| README.md | ||
| regenerate.bash | ||
| test.bash | ||
Next Generation Go Protocol Buffers
WARNING: This repository is in active development. There are no guarantees about API stability. Breaking changes will occur until a stable release is made and announced.
This repository is for the development of the next major Go implementation of protocol buffers. This library makes breaking API changes relative to the existing Go protobuf library. Of particular note, this API aims to make protobuf reflection a first-class feature of the API and implements the protobuf ecosystem in terms of reflection.
Design Documents
List of relevant design documents:
Contributing
We appreciate community contributions. See CONTRIBUTING.md.
Reporting Issues
Issues regarding the new API can be filed at
github.com/golang/protobuf.
Please use a APIv2: prefix in the title to make it clear that
the issue is regarding the new API work.