Go support for Google's protocol buffers
Go to file
Joe Tsai b2107fbd8d reflect/protodesc: robustify dependency resolution implementation
Overview of changes:
* Add an option that specifies whether to replace unresolvable references
with a placeholder instead of producing an error. Since the prior behavior
produced placeholders (not always), we default to that behavior for now,
but will enable strict resolving in a future CL.
* The option is not yet exported because there is concern about what the
public API should look like. This will be exposed in a future CL.
* Unlike before, we now permit placeholders for unresolvable enum values.
* We implement relative name resolution logic.
* We handle the case where the type is unknown, but type_name is specified.
In such a case, we populate both FieldDescriptor.{Enum,Message} and leave
the FieldDescriptor.Kind with the zero value. If the type_name happened
to resolve, we use that to determine the type.
* If a placeholder is used to represent a relative name,
the FullName reports an invalid full name with a "*." prefix.

Change-Id: Ifa8c750423c488fb9324eec4d033a2f251505fda
Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/184317
Reviewed-by: Damien Neil <dneil@google.com>
2019-07-03 19:17:36 +00:00
benchmarks benchmarks: add general-purpose benchmarks directory 2019-06-24 19:20:48 +00:00
cmd all: remove dependency on proto v1 2019-07-03 04:59:17 +00:00
compiler/protogen all: remove dependency on proto v1 2019-07-03 04:59:17 +00:00
encoding encoding: avoid direct access to XXX_unrecognized 2019-07-03 05:09:36 +00:00
internal reflect/protodesc: robustify dependency resolution implementation 2019-07-03 19:17:36 +00:00
proto all: remove dependency on proto v1 2019-07-03 04:59:17 +00:00
reflect reflect/protodesc: robustify dependency resolution implementation 2019-07-03 19:17:36 +00:00
runtime internal/fileinit: remove package 2019-06-20 19:35:23 +00:00
testing/prototest types/dynamicpb: add dynamic message type 2019-06-24 19:50:03 +00:00
types all: remove protoreflect.Message.Len 2019-06-25 21:59:46 +00:00
.gitignore cmd/protoc-gen-go/testdata: ignore go.sum 2019-03-11 20:19:03 +00:00
.travis.yml .travis.yml: configure for OSX 2019-03-13 18:04:08 +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
download_benchdata.bash proto: add benchmark using protobuf repo test data 2019-06-20 20:38:50 +00:00
go.mod internal/fileinit: remove package 2019-06-20 19:35:23 +00:00
go.sum internal/fileinit: remove package 2019-06-20 19:35:23 +00:00
integration_test.go proto: add benchmark using protobuf repo test data 2019-06-20 20:38:50 +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 internal/cmd/generate-protos: generate test for testdata 2019-03-11 19:40:53 +00:00
test.bash internal/cmd/generate-protos: generate test for testdata 2019-03-11 19:40:53 +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.