Google Git
Sign in
go / protobuf / 5ae10aa9f09c56d762d7b7df890c8065c4824c1f
commit5ae10aa9f09c56d762d7b7df890c8065c4824c1f[log] [tgz]
authorJoe Tsai <joetsai@digital-static.net>Thu Jul 11 18:23:08 2019 -0700
committerJoe Tsai <joetsai@digital-static.net>Mon Jul 15 21:07:58 2019 +0000
treec8f5df837e4e0f6d9e4dc55a0d4b5edaf0fa33e0
parentaf57087245ed29594751a2cd47c3ca4d7fb8dfe9 [diff]
encoding: unify MessageSet extension handling logic

This CL unifies common MessageSet logic in prototext and protojson
into the messageset package. While we are at it, also enable
MessageSet support only if the proto1_legacy build flag is enabled.

Change-Id: I1a7d475e8bb1dad61ecd286df45e4239e5bef072
Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/185898
Reviewed-by: Damien Neil <dneil@google.com>
9 files changed
tree: c8f5df837e4e0f6d9e4dc55a0d4b5edaf0fa33e0
  1. benchmarks/
  2. cmd/
  3. compiler/
  4. encoding/
  5. internal/
  6. proto/
  7. reflect/
  8. runtime/
  9. testing/
  10. types/
  11. .gitignore
  12. .travis.yml
  13. AUTHORS
  14. CONTRIBUTING.md
  15. CONTRIBUTORS
  16. go.mod
  17. go.sum
  18. integration_test.go
  19. LICENSE
  20. PATENTS
  21. README.md
  22. regenerate.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.