d025c95110
The proto package tests often test several variations of messages with a similar shape. For example, most tests are performed with a proto2 message with a regular field, a proto2 message with an extension field, and a proto3 message. Add a protobuild package which can initialize all these variations from a single template. For example, these three messages: &testpb.TestAllTypes{OptionalInt32: proto.Int32(1)} &test3pb.TestAllTypes{OptionalInt32: 1} m := &testpb.TestAllExtensions{} proto.SetExtension(m, &testpb.E_OptionalInt32, 1) can all be constructed from the template: protobuild.Message{"optional_int32": 1} This reduces redundancy in tests and will make it more practical to test alternative code generators. Change-Id: I3245a4bf74ee1bce957bc772fed513d427720677 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/217457 Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com> |
||
---|---|---|
cmd | ||
compiler/protogen | ||
encoding | ||
internal | ||
proto | ||
reflect | ||
runtime | ||
testing | ||
types | ||
.gitignore | ||
.travis.yml | ||
AUTHORS | ||
CONTRIBUTING.md | ||
CONTRIBUTORS | ||
go.mod | ||
go.sum | ||
integration_test.go | ||
LICENSE | ||
PATENTS | ||
README.md | ||
regenerate.bash | ||
release.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.