Skip to content

Conversation

@lukesneeringer
Copy link
Contributor

No description provided.

@lukesneeringer lukesneeringer requested a review from a team as a code owner February 9, 2021 17:57
@google-cla google-cla bot added the cla: yes label Feb 9, 2021
Base automatically changed from master to main February 10, 2021 22:08
Copy link

@mkistler mkistler left a 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.

Comment on lines +95 to +110
### 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.

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

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.

Suggested change
In APIs defined in protocol buffers, public comments **must** be included over
Documentation **must** be included for

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants