42fa50da34
The golden tests are sensitive to the exact version used: * Protobuf toolchain since the generated Descriptor is dependendent on protoc (for example, default json_names were auto-populated in later versions of protoc) * Go toolchain since the generated .pb.go files is dependent on the exact output of gofmt and the gzip compression used. There are other areas where it depends on unstable output, but the above are the major causes. Since test.bash ensures that the golden tests are run with exact versions of the protobuf and Go toolchains, we can ensure that the tests are reproducible across different developer workstations. Thus, we add a "golden" build tag to disable them for normal invocations of "go test ./..." and only run them if test.bash is run. If test.bash is ever updated with newer versions, the golden testdata can be updated at the same time. Change-Id: Ia2b7b039aad2ddaef7652e332215bf9403a6d856 Reviewed-on: https://go-review.googlesource.com/c/142458 Reviewed-by: Damien Neil <dneil@google.com> |
||
---|---|---|
cmd | ||
internal | ||
protogen | ||
reflect | ||
.gitignore | ||
.travis.yml | ||
AUTHORS | ||
CONTRIBUTING.md | ||
CONTRIBUTORS | ||
go.mod | ||
go.sum | ||
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.