|author||Damien Neil <firstname.lastname@example.org>||Wed Feb 05 16:26:45 2020 -0800|
|committer||Damien Neil <email@example.com>||Thu Feb 06 19:43:25 2020 +0000|
all: tests, tweaks for lazy extension decoding Add a test to confirm that extensions are lazily decoded when we expect. Drop the UnmarshalDefaultResolver flag. I added it thinking for some reason that internal/impl couldn't depend on protoregistry; since it can (and does), it's simpler to just test if the resolver is the expected value. Use a default set of options when lazily unmarshaling extensions. Change-Id: Ied7666ffdc3bf90630260a80c9568d9a945048bc Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/218038 Reviewed-by: Joe Tsai <firstname.lastname@example.org>
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.
List of relevant design documents:
We appreciate community contributions. See CONTRIBUTING.md.
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.