fix(protobuf): use DynamicMessage for MESSAGE-type extension defaults #14900
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed extension registry initialization for MESSAGE-type extensions by using
DynamicMessage.getDefaultInstance(FieldDescriptor) instead of
FieldDescriptorProto.getDefaultInstanceForType(). The latter would simply
get a default instance of a FieldDesriptorProto message, clearly not our
intention.
Added test coverage for MESSAGE-type extensions using messageF.proto, which
exercises the case where extension values are message types rather than
primitives or enums.
Verified that this fixes the customer issue by running the datahub-protobuf
CLI against the files provided in https://acrylsupport.zendesk.com/agent/tickets/4845
🤖 Generated with Claude Code