-
Notifications
You must be signed in to change notification settings - Fork 551
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(AIP-122): clarify shortening rules for nested collections #1372
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think I'd still like to hear more about the intended uses for singular and plurals in a meeting - I haven't been tracking this closely enough.
They are used for a few different things but mostly to give an authoritative field within the annotation to define the words so that those usages of the resource singular & plural forms aren't left to guess it from the |
While implementing rules for
singular
/plural
presence inpattern
values including the nested collection exception, I noticed that the guidance was vague for each specific field in thegoogle.api.resource
annotation.