[#394] Don't use generics when marshalling collections #401
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* A temporary workaround for the issue. Full support for generic parameter types will need to be added to type mirroring
ryanemerson
reviewed
Jan 13, 2025
| @@ -719,7 +721,11 @@ protected void generateWriteMethodBody(IndentWriter iw, ProtoMessageTypeMetadata | |||
| mapFieldMetadata.getValue().getJavaTypeName() | |||
| ); | |||
| } else { | |||
| iw.printf("java.util.Collection<%s>", fieldMetadata.getJavaTypeName()); | |||
| if (useGenerics) { | |||
There was a problem hiding this comment.
I know, I wanted to keep the code around for when I do it properly
|
Thanks @tristantarrant, please backport to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #394