fix(AIP-123): allow name in nested messages #1325
Merged
Conversation
This file contains hidden or 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
andrei-scripniciuc
suggested changes
Jan 24, 2024
Yep! Done. |
andrei-scripniciuc
approved these changes
Jan 24, 2024
gcf-merge-on-green bot
pushed a commit
that referenced
this pull request
Jan 25, 2024
🤖 I have created a release *beep* *boop* --- ## [1.63.3](https://togithub.com/googleapis/api-linter/compare/v1.63.2...v1.63.3) (2024-01-25) ### Bug Fixes * **AIP-123:** allow name in nested messages ([#1325](https://togithub.com/googleapis/api-linter/issues/1325)) ([16316a5](https://togithub.com/googleapis/api-linter/commit/16316a5405bd967e926a1482f3bd1e85e1c45eed)) --- This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).
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.
It is reasonable to allow the use of a
namefield in a nested message since nested messages are most often authored as a small piece of a larger message, thus never really candidates for being a resource.