-
Notifications
You must be signed in to change notification settings - Fork 69
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: list oneofs in docstring #1030
Conversation
This message has the following `oneof`_ fields (mutually exclusive fields). | ||
For each oneof, at most one member field can be set at the same time. | ||
Setting any member of the oneof automatically clears all other | ||
members. |
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.
@@ -512,13 +512,26 @@ class DeleteFeedRequest(proto.Message): | |||
class OutputConfig(proto.Message): | |||
r"""Output configuration for export assets destination. | |||
|
|||
This message has the following `oneof`_ fields (mutually exclusive fields). |
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.
@dandhlee This is a concrete example of the new docstring with the oneof information.
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.
Will take a look, intuition tells me it'll just show up as `oneof`_
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.
Sadly it doesn't get parsed, but I'll be happy to include support for it C:
Fixes #713
FIeld attributes state which oneof they are part of.
If a message has a oneof with more than 1 member field, the docstring includes a short explanation of oneofs
and a list of the oneofs in the message.The list looks a bit odd in the generated docs (output of
nox -s docs
/ what's published to googleapis.dev) - suggestions on better ways to present the information are very appreciated.@dandhlee Do you have an idea of how this docstring change would look in Cloud RAD?