fix: Use type name instead of full type declaration #5679
Merged
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.
References to other Issues or PRs
Fixes #5678
Have you read the Contributing Guidelines? Yes
Brief description of what is fixed or changed
When using
standalone=true, this would end up asresponse := m.extPackageNamepb.ResponseObjectwhere extPackageNamepb is the import alias for the main proto type package. This resulted in invalid syntax and failed to compile.Seems to have been introduced here #5510 which went out in the latest release. Noticed this issue when bumping protos, and the registering of my gateway handler failed to compile
Other comments
for reference, current behavior vs with this fix, using the response_body_service.proto example:
Current Behavior
New behavior