mirror/protobuf-go
1
0
Fork 0
mirror of https://github.com/protocolbuffers/protobuf-go.git synced 2025-01-18 13:11:16 +00:00
Code Issues Packages Projects Releases Wiki Activity
protobuf-go/internal/testprotos/legacy/legacy.proto

73 lines
3.4 KiB
Protocol Buffer
Raw Normal View History

internal/testprotos/legacy: initial commit Add a corpus of generated protobuf messages generated at specific versions of protoc-gen-go to ensure that we continue to support for generated messages that have may never be updated. Change-Id: I04a1b74306f471d7c99f5daf52399a5bd9adcbbc Reviewed-on: https://go-review.googlesource.com/c/148831 Reviewed-by: Herbie Ong <herbie@google.com>
2018-11-11 17:56:21 -08:00
// Copyright 2018 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.
syntax = "proto3";
package google.golang.org;
all: change module to google.golang.org/protobuf Temporarily remove go.mod, since we can't generate an accurate one until the corresponding v1 change is submitted. Change-Id: I1e1ad97f2b455e33f61ffaeb8676289795e47e72 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/177000 Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com>
2019-05-13 23:55:40 -07:00
option go_package = "google.golang.org/protobuf/internal/testprotos/legacy";
internal/testprotos/legacy: initial commit Add a corpus of generated protobuf messages generated at specific versions of protoc-gen-go to ensure that we continue to support for generated messages that have may never be updated. Change-Id: I04a1b74306f471d7c99f5daf52399a5bd9adcbbc Reviewed-on: https://go-review.googlesource.com/c/148831 Reviewed-by: Herbie Ong <herbie@google.com>
2018-11-11 17:56:21 -08:00
// This file imports other files generated from a build of protoc-gen-go
// locked to a specific version. For all imports, they were built using
// Go v1.11 and protoc v3.5.1. This package is used to test compatibility with
// checked in generated code that cannot easily change.
// As such, there should never be a need to update these generated files.
//
// The specific version of protoc-gen-go used is encoded in the file path:
// $NAME.$VERSION-$COMMIT_DATE-$COMMIT_HASH/test.proto
// The oldest supported version of protoc-gen-go is 2fc053c5,
// which finished adding descriptor methods to all protobuf types.
internal/cmd/generate-protos: initial commit Create a single binary for handling generation of protos. This replaces previous logic spread throughout the repo in: * regenerate.bash * cmd/protoc-gen-go/golden_test.go * cmd/protoc-gen-go-grpc/golden_test.go * (indirectly) internal/protogen/goldentest One of the problems with the former approaches is that they relied on a version of protoc that was specific to a developer's workstation. This meant that the result of generation was not hermetic. To address this, we rely on the hard-coded version of protobuf specified in the test.bash script. A summary of changes in this CL are: * The internal_gengo.GenerateFile and internal_gengogrpc.GenerateFile functions are unified to have consistent signatures. It seems that the former accepted a *protogen.GeneratedFile to support v1 where gRPC code was generated into the same file as the base .pb.go file. However, the same functionality can be achieved by having the function return the generated file object. * The test.bash script patches the protobuf toolchain to have properly specified go_package options in each proto source file. * The test.bash script accepts a "-regenerate" argument. * Add generation for the well-known types. Contrary to how these were laid out in the v1 repo, all the well-known types are placed in the same Go package. * Add generation for the conformance proto. * Remove regenerate.bash * Remove internal/protogen * Remove cmd/protoc-gen-go/golden_test.go * Remove cmd/protoc-gen-go-grpc/golden_test.go * Add cmd/protoc-gen-go/annotation_test.go Change-Id: I4a1a97ae6f66e2fabcf4e4d292c95ab2a2db0248 Reviewed-on: https://go-review.googlesource.com/c/164477 Reviewed-by: Damien Neil <dneil@google.com>
2019-02-27 21:46:29 -08:00
import "legacy/proto2.v0.0.0-20160225-2fc053c5/test.proto";
import "legacy/proto3.v0.0.0-20160225-2fc053c5/test.proto";
internal/testprotos/legacy: initial commit Add a corpus of generated protobuf messages generated at specific versions of protoc-gen-go to ensure that we continue to support for generated messages that have may never be updated. Change-Id: I04a1b74306f471d7c99f5daf52399a5bd9adcbbc Reviewed-on: https://go-review.googlesource.com/c/148831 Reviewed-by: Herbie Ong <herbie@google.com>
2018-11-11 17:56:21 -08:00
// Changes from 20160225 to 20160519:
// * Nothing noteworthy to generated code
internal/cmd/generate-protos: initial commit Create a single binary for handling generation of protos. This replaces previous logic spread throughout the repo in: * regenerate.bash * cmd/protoc-gen-go/golden_test.go * cmd/protoc-gen-go-grpc/golden_test.go * (indirectly) internal/protogen/goldentest One of the problems with the former approaches is that they relied on a version of protoc that was specific to a developer's workstation. This meant that the result of generation was not hermetic. To address this, we rely on the hard-coded version of protobuf specified in the test.bash script. A summary of changes in this CL are: * The internal_gengo.GenerateFile and internal_gengogrpc.GenerateFile functions are unified to have consistent signatures. It seems that the former accepted a *protogen.GeneratedFile to support v1 where gRPC code was generated into the same file as the base .pb.go file. However, the same functionality can be achieved by having the function return the generated file object. * The test.bash script patches the protobuf toolchain to have properly specified go_package options in each proto source file. * The test.bash script accepts a "-regenerate" argument. * Add generation for the well-known types. Contrary to how these were laid out in the v1 repo, all the well-known types are placed in the same Go package. * Add generation for the conformance proto. * Remove regenerate.bash * Remove internal/protogen * Remove cmd/protoc-gen-go/golden_test.go * Remove cmd/protoc-gen-go-grpc/golden_test.go * Add cmd/protoc-gen-go/annotation_test.go Change-Id: I4a1a97ae6f66e2fabcf4e4d292c95ab2a2db0248 Reviewed-on: https://go-review.googlesource.com/c/164477 Reviewed-by: Damien Neil <dneil@google.com>
2019-02-27 21:46:29 -08:00
import "legacy/proto2.v0.0.0-20160519-a4ab9ec5/test.proto";
import "legacy/proto3.v0.0.0-20160519-a4ab9ec5/test.proto";
internal/testprotos/legacy: initial commit Add a corpus of generated protobuf messages generated at specific versions of protoc-gen-go to ensure that we continue to support for generated messages that have may never be updated. Change-Id: I04a1b74306f471d7c99f5daf52399a5bd9adcbbc Reviewed-on: https://go-review.googlesource.com/c/148831 Reviewed-by: Herbie Ong <herbie@google.com>
2018-11-11 17:56:21 -08:00
// Changes from 20160519 to 20180125:
// * Removed ExtensionMap method and XXX_extensions field from messages
// * Added embedded proto.XXX_InternalExtensions field to messages
// * Added proto.ExtensionDesc.Filename field
// * Added registration for file descriptor
// * Added Get accessor methods for all fields in proto3 messages
// * Proto3 repeated primitives are packed by default
internal/cmd/generate-protos: initial commit Create a single binary for handling generation of protos. This replaces previous logic spread throughout the repo in: * regenerate.bash * cmd/protoc-gen-go/golden_test.go * cmd/protoc-gen-go-grpc/golden_test.go * (indirectly) internal/protogen/goldentest One of the problems with the former approaches is that they relied on a version of protoc that was specific to a developer's workstation. This meant that the result of generation was not hermetic. To address this, we rely on the hard-coded version of protobuf specified in the test.bash script. A summary of changes in this CL are: * The internal_gengo.GenerateFile and internal_gengogrpc.GenerateFile functions are unified to have consistent signatures. It seems that the former accepted a *protogen.GeneratedFile to support v1 where gRPC code was generated into the same file as the base .pb.go file. However, the same functionality can be achieved by having the function return the generated file object. * The test.bash script patches the protobuf toolchain to have properly specified go_package options in each proto source file. * The test.bash script accepts a "-regenerate" argument. * Add generation for the well-known types. Contrary to how these were laid out in the v1 repo, all the well-known types are placed in the same Go package. * Add generation for the conformance proto. * Remove regenerate.bash * Remove internal/protogen * Remove cmd/protoc-gen-go/golden_test.go * Remove cmd/protoc-gen-go-grpc/golden_test.go * Add cmd/protoc-gen-go/annotation_test.go Change-Id: I4a1a97ae6f66e2fabcf4e4d292c95ab2a2db0248 Reviewed-on: https://go-review.googlesource.com/c/164477 Reviewed-by: Damien Neil <dneil@google.com>
2019-02-27 21:46:29 -08:00
import "legacy/proto2.v1.0.0-20180125-92554152/test.proto";
import "legacy/proto3.v1.0.0-20180125-92554152/test.proto";
internal/testprotos/legacy: initial commit Add a corpus of generated protobuf messages generated at specific versions of protoc-gen-go to ensure that we continue to support for generated messages that have may never be updated. Change-Id: I04a1b74306f471d7c99f5daf52399a5bd9adcbbc Reviewed-on: https://go-review.googlesource.com/c/148831 Reviewed-by: Herbie Ong <herbie@google.com>
2018-11-11 17:56:21 -08:00
// Changes from 20180125 to 20180430:
// * Added XXX_unrecognized field to proto3 messages
// * Added XXX_NoUnkeyedLiteral field to messages
// * Added XXX_sizecache field to messages
// * Added XXX_Unmarshal method to messages
// * Added XXX_Marshal method to messages
// * Added XXX_Merge method to messages
// * Added XXX_Size method to messages
// * Added XXX_DiscardUnknown method to messages
// * Added dependency on proto.InternalMessageInfo for table-driven logic
// * Added registration for map types
internal/cmd/generate-protos: initial commit Create a single binary for handling generation of protos. This replaces previous logic spread throughout the repo in: * regenerate.bash * cmd/protoc-gen-go/golden_test.go * cmd/protoc-gen-go-grpc/golden_test.go * (indirectly) internal/protogen/goldentest One of the problems with the former approaches is that they relied on a version of protoc that was specific to a developer's workstation. This meant that the result of generation was not hermetic. To address this, we rely on the hard-coded version of protobuf specified in the test.bash script. A summary of changes in this CL are: * The internal_gengo.GenerateFile and internal_gengogrpc.GenerateFile functions are unified to have consistent signatures. It seems that the former accepted a *protogen.GeneratedFile to support v1 where gRPC code was generated into the same file as the base .pb.go file. However, the same functionality can be achieved by having the function return the generated file object. * The test.bash script patches the protobuf toolchain to have properly specified go_package options in each proto source file. * The test.bash script accepts a "-regenerate" argument. * Add generation for the well-known types. Contrary to how these were laid out in the v1 repo, all the well-known types are placed in the same Go package. * Add generation for the conformance proto. * Remove regenerate.bash * Remove internal/protogen * Remove cmd/protoc-gen-go/golden_test.go * Remove cmd/protoc-gen-go-grpc/golden_test.go * Add cmd/protoc-gen-go/annotation_test.go Change-Id: I4a1a97ae6f66e2fabcf4e4d292c95ab2a2db0248 Reviewed-on: https://go-review.googlesource.com/c/164477 Reviewed-by: Damien Neil <dneil@google.com>
2019-02-27 21:46:29 -08:00
import "legacy/proto2.v1.1.0-20180430-b4deda09/test.proto";
import "legacy/proto3.v1.1.0-20180430-b4deda09/test.proto";
internal/testprotos/legacy: initial commit Add a corpus of generated protobuf messages generated at specific versions of protoc-gen-go to ensure that we continue to support for generated messages that have may never be updated. Change-Id: I04a1b74306f471d7c99f5daf52399a5bd9adcbbc Reviewed-on: https://go-review.googlesource.com/c/148831 Reviewed-by: Herbie Ong <herbie@google.com>
2018-11-11 17:56:21 -08:00
// Changes from 20180430 to 20180814:
// * Added "proto3" struct tag to all fields in proto3 messages
internal/cmd/generate-protos: initial commit Create a single binary for handling generation of protos. This replaces previous logic spread throughout the repo in: * regenerate.bash * cmd/protoc-gen-go/golden_test.go * cmd/protoc-gen-go-grpc/golden_test.go * (indirectly) internal/protogen/goldentest One of the problems with the former approaches is that they relied on a version of protoc that was specific to a developer's workstation. This meant that the result of generation was not hermetic. To address this, we rely on the hard-coded version of protobuf specified in the test.bash script. A summary of changes in this CL are: * The internal_gengo.GenerateFile and internal_gengogrpc.GenerateFile functions are unified to have consistent signatures. It seems that the former accepted a *protogen.GeneratedFile to support v1 where gRPC code was generated into the same file as the base .pb.go file. However, the same functionality can be achieved by having the function return the generated file object. * The test.bash script patches the protobuf toolchain to have properly specified go_package options in each proto source file. * The test.bash script accepts a "-regenerate" argument. * Add generation for the well-known types. Contrary to how these were laid out in the v1 repo, all the well-known types are placed in the same Go package. * Add generation for the conformance proto. * Remove regenerate.bash * Remove internal/protogen * Remove cmd/protoc-gen-go/golden_test.go * Remove cmd/protoc-gen-go-grpc/golden_test.go * Add cmd/protoc-gen-go/annotation_test.go Change-Id: I4a1a97ae6f66e2fabcf4e4d292c95ab2a2db0248 Reviewed-on: https://go-review.googlesource.com/c/164477 Reviewed-by: Damien Neil <dneil@google.com>
2019-02-27 21:46:29 -08:00
import "legacy/proto2.v1.2.0-20180814-aa810b61/test.proto";
import "legacy/proto3.v1.2.0-20180814-aa810b61/test.proto";
internal/impl: fix legacy logic to know about the new XXX_OneofWrappers method The XXX_OneofWrappers method is a simplified way to obtain the wrapper structs compared the previous XXX_OneofFuncs method which returned far more information that was strictly necessary. Change-Id: I2670506a2a8f7e8e724846b8c4083e7995371007 Reviewed-on: https://go-review.googlesource.com/c/151679 Reviewed-by: Herbie Ong <herbie@google.com>
2018-11-28 23:43:49 -08:00
// Changes from 20180814 to 20181126:
// * Changed the XXX_OneofFuncs method to XXX_OneofWrappers
// * Various syntactical changes to make the output more consistent
internal/cmd/generate-protos: initial commit Create a single binary for handling generation of protos. This replaces previous logic spread throughout the repo in: * regenerate.bash * cmd/protoc-gen-go/golden_test.go * cmd/protoc-gen-go-grpc/golden_test.go * (indirectly) internal/protogen/goldentest One of the problems with the former approaches is that they relied on a version of protoc that was specific to a developer's workstation. This meant that the result of generation was not hermetic. To address this, we rely on the hard-coded version of protobuf specified in the test.bash script. A summary of changes in this CL are: * The internal_gengo.GenerateFile and internal_gengogrpc.GenerateFile functions are unified to have consistent signatures. It seems that the former accepted a *protogen.GeneratedFile to support v1 where gRPC code was generated into the same file as the base .pb.go file. However, the same functionality can be achieved by having the function return the generated file object. * The test.bash script patches the protobuf toolchain to have properly specified go_package options in each proto source file. * The test.bash script accepts a "-regenerate" argument. * Add generation for the well-known types. Contrary to how these were laid out in the v1 repo, all the well-known types are placed in the same Go package. * Add generation for the conformance proto. * Remove regenerate.bash * Remove internal/protogen * Remove cmd/protoc-gen-go/golden_test.go * Remove cmd/protoc-gen-go-grpc/golden_test.go * Add cmd/protoc-gen-go/annotation_test.go Change-Id: I4a1a97ae6f66e2fabcf4e4d292c95ab2a2db0248 Reviewed-on: https://go-review.googlesource.com/c/164477 Reviewed-by: Damien Neil <dneil@google.com>
2019-02-27 21:46:29 -08:00
import "legacy/proto2.v1.2.1-20181126-8d0c54c1/test.proto";
import "legacy/proto3.v1.2.1-20181126-8d0c54c1/test.proto";
internal/testprotos/legacy: initial commit Add a corpus of generated protobuf messages generated at specific versions of protoc-gen-go to ensure that we continue to support for generated messages that have may never be updated. Change-Id: I04a1b74306f471d7c99f5daf52399a5bd9adcbbc Reviewed-on: https://go-review.googlesource.com/c/148831 Reviewed-by: Herbie Ong <herbie@google.com>
2018-11-11 17:56:21 -08:00
message Legacy {
google.golang.org.proto2_20160225.Message f1 = 1;
google.golang.org.proto3_20160225.Message f2 = 2;
google.golang.org.proto2_20160519.Message f3 = 3;
google.golang.org.proto3_20160519.Message f4 = 4;
google.golang.org.proto2_20180125.Message f5 = 5;
google.golang.org.proto3_20180125.Message f6 = 6;
google.golang.org.proto2_20180430.Message f7 = 7;
google.golang.org.proto3_20180430.Message f8 = 8;
google.golang.org.proto2_20180814.Message f9 = 9;
google.golang.org.proto3_20180814.Message f10 = 10;
internal/impl: fix legacy logic to know about the new XXX_OneofWrappers method The XXX_OneofWrappers method is a simplified way to obtain the wrapper structs compared the previous XXX_OneofFuncs method which returned far more information that was strictly necessary. Change-Id: I2670506a2a8f7e8e724846b8c4083e7995371007 Reviewed-on: https://go-review.googlesource.com/c/151679 Reviewed-by: Herbie Ong <herbie@google.com>
2018-11-28 23:43:49 -08:00
google.golang.org.proto2_20181126.Message f11 = 11;
google.golang.org.proto3_20181126.Message f12 = 12;
internal/testprotos/legacy: initial commit Add a corpus of generated protobuf messages generated at specific versions of protoc-gen-go to ensure that we continue to support for generated messages that have may never be updated. Change-Id: I04a1b74306f471d7c99f5daf52399a5bd9adcbbc Reviewed-on: https://go-review.googlesource.com/c/148831 Reviewed-by: Herbie Ong <herbie@google.com>
2018-11-11 17:56:21 -08:00
}
Reference in New Issue Copy Permalink