mirror of
https://github.com/protocolbuffers/protobuf-go.git
synced 2025-01-04 02:38:50 +00:00
90fe996bd1
In order for the v2 rollout to be as seamless as possible, we need to support the situation where a v2 message depends on some other generated v1 message that may be stale and does not support the v2 API. In such a situation, there needs to be some way to wrap a legacy message or enum in such a way that it satisfies the v2 API. This wrapping is comprised of two parts: 1) Deriving an enum or message descriptor 2) Providing an reflection implementation for messages This CL addresses part 1 (while part 2 has already been partially implemented, since the implementation applies to both v1 and v2). To derive the enum and message descriptor we rely on a mixture of parsing the raw descriptor proto and also introspection on the fields in the message. Methods for obtaining the raw descriptor protos were added in February, 2016, and so has not always been available. For that reason, we attempt to derive as much information from the Go type as possible. As part of this change, we modify prototype to be able to create multiple standalone messages as a set. This is needed since cyclic dependencies is allowed between messages within a single proto file. Change-Id: I71aaf5f977faf9fba03c370b1ee17b3758ce60a6 Reviewed-on: https://go-review.googlesource.com/c/143539 Reviewed-by: Damien Neil <dneil@google.com> |
||
|---|---|---|
| .. | ||
| legacy_enum.go | ||
| legacy_file.go | ||
| legacy_message.go | ||
| legacy_proto2_test.go | ||
| legacy_proto3_test.go | ||
| legacy_test.go | ||
| message_field.go | ||
| message_test.go | ||
| message.go | ||
| pointer_reflect.go | ||
| pointer_unsafe.go | ||