-
Notifications
You must be signed in to change notification settings - Fork 3
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-192 – Documentation #25
base: main
Are you sure you want to change the base?
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.
Looks good. 👍
I left some suggestions to change/remove material that seems only applicable to protobuf, but I would be okay with merging the PR as is and addressing this points later.
### Internal comments | ||
|
||
<!-- TODO: This does not work outside of Google. | ||
We should probably try to get that fixed. --> | ||
|
||
Comments **may** be explicitly marked as internal by wrapping internal content | ||
in `(--` and `--)`. | ||
|
||
Non-public links, internal implementation notes (such as `TODO` and `FIXME` | ||
directives), and other such material **must** be marked as internal. | ||
|
||
**Note:** In IDLs using code comment syntax, comments **should** use only | ||
leading comments (not trailing comments or detached comments). In particular, | ||
comments **must not** use both a leading and trailing comment to describe any | ||
component, because this is a common source of inadvertent omissions of the | ||
internal content annotation. |
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.
Suggest that we remove this -- it apparently doesn't work outside Google and there is no OAS analog.
|
||
## Guidance | ||
|
||
In APIs defined in protocol buffers, public comments **must** be included over |
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.
Let's not restrict this to protocol buffers.
In APIs defined in protocol buffers, public comments **must** be included over | |
Documentation **must** be included for |
No description provided.