-
Notifications
You must be signed in to change notification settings - Fork 510
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
feat(AIP-202): add enriched Field descriptor AIP #1216
Conversation
cc @slevenick @dizcology @ibelle @amanda-tarafa as an FYI |
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.
Hi! Absolutely thrilled this is being established!
Would really like to see equality
musts emphasized as much or more than normalize
requirements mays
Co-authored-by: Amanda Tarafa Mas <[email protected]>
Co-authored-by: Amanda Tarafa Mas <[email protected]>
To the folks CC'd, I'd like to put a review goal of End of Week on this if possible. It is necessary to unblock the supporting work I have lined up for publishing all of this. |
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.
Yup, the equivalence text looks good to me.
@loudej @slevenick @amanda-tarafa one more bump on this. I plan to submit it EoW if there is no other feedback. |
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.
LGMT!
Resolved offline, many others have approved.
Introduce AIP-202 (chosen as one previous of AIP-203 regarding
google.api.field_behavior
) to provide guidance on the usage of the forthcominggoogle.api.Field
type andgoogle.api.field
extension.This will support the in progress AIP-129 and further support a future change to AIP-155.
Internal bug http://b/300315543