Go support for Google's protocol buffers
Go to file
Joe Tsai e1f8d50e17 reflect/protodesc: split descriptor related functionality from prototype
In order to generate descriptor.proto, the generated code would want to depend
on the prototype package to construct the reflection data structures.
However, this is a problem since descriptor itself is one of the dependencies
for prototype. To break this dependency, we do the following:
* Avoid using concrete *descriptorpb.XOptions messages in the public API, and
instead just use protoreflect.ProtoMessage. We do lose some type safety here
as a result.
* Use protobuf reflection to interpret the Options message.
* Split out NewFileFromDescriptorProto into a separate protodesc package since
constructing protobuf reflection from the descriptor proto obviously depends
on the descriptor protos themselves.

As part of this CL, we check in a pre-generated version of descriptor and plugin
that supports protobuf reflection natively and switchover all usages of those
protos to the new definitions. These files were generated by protoc-gen-go
from CL/150074, but hand-modified to remove dependencies on the v1 proto runtime.

Change-Id: I81e03c42eeab480b03764e2fcbe1aae0e058fc57
Reviewed-on: https://go-review.googlesource.com/c/152020
Reviewed-by: Damien Neil <dneil@google.com>
2018-12-05 00:38:30 +00:00
cmd reflect/protodesc: split descriptor related functionality from prototype 2018-12-05 00:38:30 +00:00
encoding/textpb internal/legacy: extract legacy support out from the impl package 2018-11-30 23:16:16 +00:00
internal reflect/protodesc: split descriptor related functionality from prototype 2018-12-05 00:38:30 +00:00
proto encoding/textpb: initial implementation of textproto marshaling 2018-11-29 23:06:35 +00:00
protogen reflect/protodesc: split descriptor related functionality from prototype 2018-12-05 00:38:30 +00:00
reflect reflect/protodesc: split descriptor related functionality from prototype 2018-12-05 00:38:30 +00:00
runtime reflect/protodesc: split descriptor related functionality from prototype 2018-12-05 00:38:30 +00:00
types reflect/protodesc: split descriptor related functionality from prototype 2018-12-05 00:38:30 +00:00
.gitignore cmd/protoc-gen-go-grpc: add gRPC code generator 2018-09-27 19:32:34 +00:00
.travis.yml test.bash: use repo-local cache 2018-09-06 19:58:40 +00:00
AUTHORS AUTHORS, CONTRIBUTORS, LICENSE, PATENTS: initial commit 2018-08-07 22:39:48 +00:00
CONTRIBUTING.md CONTRIBUTING.md: add pre-push hook instructions 2018-08-07 23:58:41 +00:00
CONTRIBUTORS AUTHORS, CONTRIBUTORS, LICENSE, PATENTS: initial commit 2018-08-07 22:39:48 +00:00
go.mod reflect/protodesc: split descriptor related functionality from prototype 2018-12-05 00:38:30 +00:00
go.sum reflect/protodesc: split descriptor related functionality from prototype 2018-12-05 00:38:30 +00:00
LICENSE AUTHORS, CONTRIBUTORS, LICENSE, PATENTS: initial commit 2018-08-07 22:39:48 +00:00
PATENTS AUTHORS, CONTRIBUTORS, LICENSE, PATENTS: initial commit 2018-08-07 22:39:48 +00:00
README.md CONTRIBUTING.md: initial commit 2018-08-01 20:39:06 +00:00
regenerate.bash cmd/protoc-gen-go-grpc: add gRPC code generator 2018-09-27 19:32:34 +00:00
test.bash test.bash: update to go1.10.5 and go1.11.2 2018-11-19 18:05:39 +00:00

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.