mirror/protobuf-go
1
0
Fork 0
mirror of https://github.com/protocolbuffers/protobuf-go.git synced 2025-01-29 00:32:43 +00:00
Code Issues Packages Projects Releases Wiki Activity
protobuf-go/cmd/protoc-gen-go/testdata/gen_test.go

30 lines
1.6 KiB
Go
Raw Normal View History

internal/cmd/generate-protos: generate test for testdata Running "go build ./..." does not descend into testdata directories. However, the testdata in this repository is source code that is intended to build properly. We could rename the directory, but that does not test whether the generated packages can initialize properly. Thus, we generate a trivial test that simply blank imports all packages. Doing this reveals that some of the generated files have incorrect imports, leading to registration conflicts. To avoid introducing a dependency on gRPC from our go.mod file, we put the testdata directories in their own module. Also, we avoid running internal/testprotos through the grpc plugin because the servie and method definitions in that directory are more for testing proto file initialization rather than testing grpc generation. Change-Id: Iaa6a06449787a085200e31bc7606e3ac904d3180 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/164917 Reviewed-by: Damien Neil <dneil@google.com>
2019-03-01 18:11:42 -08:00
// Copyright 2019 The Go Authors. All rights reserved.
all: remove stray "." from license headers Remove a stray bit of punctuation that crept into one of the license headers and got copied around everywhere. Change-Id: Iebe4e882650ab6dab28f132b5e324e2ab0b99a73 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/220339 Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com>
2020-02-20 10:30:38 -08:00
// Use of this source code is governed by a BSD-style
internal/cmd/generate-protos: generate test for testdata Running "go build ./..." does not descend into testdata directories. However, the testdata in this repository is source code that is intended to build properly. We could rename the directory, but that does not test whether the generated packages can initialize properly. Thus, we generate a trivial test that simply blank imports all packages. Doing this reveals that some of the generated files have incorrect imports, leading to registration conflicts. To avoid introducing a dependency on gRPC from our go.mod file, we put the testdata directories in their own module. Also, we avoid running internal/testprotos through the grpc plugin because the servie and method definitions in that directory are more for testing proto file initialization rather than testing grpc generation. Change-Id: Iaa6a06449787a085200e31bc7606e3ac904d3180 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/164917 Reviewed-by: Damien Neil <dneil@google.com>
2019-03-01 18:11:42 -08:00
// license that can be found in the LICENSE file.
// Code generated by generate-protos. DO NOT EDIT.
package main
import (
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
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/annotations"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/comments"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/extensions/base"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/extensions/ext"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/extensions/extra"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/extensions/proto3"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/fieldnames"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/import_public"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/import_public/sub"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/import_public/sub2"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/imports"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/imports/fmt"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/imports/test_a_1"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/imports/test_a_2"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/imports/test_b_1"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/issue780_oneof_conflict"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/nopackage"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/proto2"
_ "google.golang.org/protobuf/cmd/protoc-gen-go/testdata/proto3"
internal/cmd/generate-protos: generate test for testdata Running "go build ./..." does not descend into testdata directories. However, the testdata in this repository is source code that is intended to build properly. We could rename the directory, but that does not test whether the generated packages can initialize properly. Thus, we generate a trivial test that simply blank imports all packages. Doing this reveals that some of the generated files have incorrect imports, leading to registration conflicts. To avoid introducing a dependency on gRPC from our go.mod file, we put the testdata directories in their own module. Also, we avoid running internal/testprotos through the grpc plugin because the servie and method definitions in that directory are more for testing proto file initialization rather than testing grpc generation. Change-Id: Iaa6a06449787a085200e31bc7606e3ac904d3180 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/164917 Reviewed-by: Damien Neil <dneil@google.com>
2019-03-01 18:11:42 -08:00
)
Reference in New Issue Copy Permalink