fix: HTTP body field messages with enums or recursive fields #1201
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
software-dov
requested review from
parthea,
busunkim96,
atulep and
vam-google
software-dov
force-pushed
the
primitive-enum
branch
2 times, most recently
from
073a4fa to
20d4b96
Compare
Minor fix for a generating unit tests for methods where the message that is the body field has a field that is an enum or a recursive field message type.
software-dov
force-pushed
the
primitive-enum
branch
from
20d4b96 to
36aa586
Compare
busunkim96
approved these changes
Feb 10, 2022
software-dov
added
the
automerge
gcf-merge-on-green
bot
removed
the
automerge
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.
Minor fix for a generating unit tests for methods where the message
that is the body field has a field that is an enum or a recursive
field message type.