fix(AIP-203): field-behavior-required ignore imported request types #1504
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.
fixes a bug where the method input type used as the starting point for the
field-behavior-required
recursion did not check if the input type itself was from the same package. It is not a super common practice in general, but appears a lot for APIs that mix in the google.iam.v1 IAM Policy service RPCs and reuse their request messages. Same thing could happen withgoogle.api.HttpBody
which is sometimes used as a RPC input type.Updates #1503