merging protos with Any fields generates a fictional, invalid proto field #113
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
So far I've only seen this in generated proto messages that have a field of type
protobuf.Any
. If one merges such a proto file with another one, a new fictional field is created in the message containing theAny
. The fictional field is is listed inside the.proto
file asnull google = XXX
, where XXX is a field number. What's even stranger is that this happens even if the "previous".proto
being merged with came from the exact same source as the current proto being generated.Reproduction steps:
copyField()
introduced in fix(merge): disable merging proto fields when both old and new versions have type==null #112:/tmp/compute.examine.0.proto
without merging with any previous proto (no--previous_proto_file_path
):/tmp/compute.examine.1.proto
from the same source, but merging with the previous/tmp/compute.examine.0.proto
(with the--previous_proto_file_path
):/tmp/compute.examine.0.proto
and/tmp/compute.examine.0.proto
The text was updated successfully, but these errors were encountered: