Google Git
Sign in
go / protobuf / c7aa53a3e0e697061ca81cc4289ea0dc85be11f1
commitc7aa53a3e0e697061ca81cc4289ea0dc85be11f1[log] [tgz]
authorDamien Neil <dneil@google.com>Wed Feb 12 10:09:24 2020 -0800
committerDamien Neil <dneil@google.com>Wed Feb 12 19:41:50 2020 +0000
treed82dc2d6c538ad91bb367f0ba51f3e0250c303c1
parentcf33a9a2745f026b6e1675348c4687eb1671bb4d [diff]
proto: refactor merge tests

Use protobuild to generate test messages, both to simplify generating
proto2/proto3/extension variants of each test where appropriate and
to make it easier to test alternative message generators in the future.

Add various additional merge tests.

Change-Id: I4ba3ce232304e1d8325543680e2b6aae61de7364
Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/219146
Reviewed-by: Joe Tsai <joetsai@google.com>
4 files changed
tree: d82dc2d6c538ad91bb367f0ba51f3e0250c303c1
  1. cmd/
  2. compiler/
  3. encoding/
  4. internal/
  5. proto/
  6. reflect/
  7. runtime/
  8. testing/
  9. types/
  10. .gitignore
  11. .travis.yml
  12. AUTHORS
  13. CONTRIBUTING.md
  14. CONTRIBUTORS
  15. go.mod
  16. go.sum
  17. integration_test.go
  18. LICENSE
  19. PATENTS
  20. README.md
  21. regenerate.bash
  22. release.bash
  23. test.bash
README.md

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.