Joe Tsai 4069211bcd protogen: use full path for generated file variable name ... Use the full path (including the extension) for the generation of the per-file variable name. Several reasons for this: * The current logic is buggy in the case where pathType == pathTypeImport since the prefix variable will be mangled with the Go import path. * The extension is technically part of the path. Thus, "path/to/foo.proto" and "path/to/foo.protodevel" are two distinctly different imports. * Style-wise, it subjectively looks better. Rather than being a mixture of camelCase and snake_case, it is all snake_case for the common case: before: ProtoFile_google_protobuf_any after: File_google_protobuf_any_proto * Since the extension is almost always ".proto", this results in a suffix of "_proto", which provides an additional layer of protection against possible name conflicts. The previous approach could possibly have a conflict between "Foo.proto" and a message named ProtoFile with a sub-message called Foo. Also, use the per-file variable name for the raw descriptor variables instead of the hashed version. Change-Id: Ic91e326b7593e5985cee6ececc60539c27fe32fe Reviewed-on: https://go-review.googlesource.com/c/164379 Reviewed-by: Damien Neil <dneil@google.com>		2019-03-01 00:13:31 +00:00
..
internal_gengo	protogen: use full path for generated file variable name	2019-03-01 00:13:31 +00:00
testdata	protogen: use full path for generated file variable name	2019-03-01 00:13:31 +00:00
golden_test.go	reflect/protodesc: split descriptor related functionality from prototype	2018-12-05 00:38:30 +00:00
main.go	protogen: add an option to rewrite import paths	2018-09-28 21:19:59 +00:00