Damien Neil 6238696abc cmd/protoc-gen-go: replicate v1 generator behavior for MessageSet extensions ... Given: package foo extend proto2.bridge.MessageSet { optional Message message_set_extension = 100; } Register the extension as a message set extension and give it the name "foo.". We really shouldn't do this in this case; the special-case treatment of extensions to MessageSet is only for extensions nested in a parent message. However, this is consistent with the behavior of the v1 generator. Match that for now. Change-Id: I919c409605a197904fd3227efc920192d484f431 Reviewed-on: https://go-review.googlesource.com/c/145957 Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com>		2018-10-30 18:46:20 +00:00
..
internal_gengo	cmd/protoc-gen-go: replicate v1 generator behavior for MessageSet extensions	2018-10-30 18:46:20 +00:00
testdata	cmd/protoc-gen-go: replicate v1 generator behavior for MessageSet extensions	2018-10-30 18:46:20 +00:00
golden_test.go	protogen: generate .meta file with code annotations	2018-10-16 17:22:41 +00:00
main.go	protogen: add an option to rewrite import paths	2018-09-28 21:19:59 +00:00