-
Notifications
You must be signed in to change notification settings - Fork 591
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
Documenting Gapic/Proto (autogen files) #1492
Comments
My initial thoughts are that users who take advantage of GAX will be a bit more advanced. That being said, it might not be unreasonable to simply link them to the proto files being used? Then from within our library we can document the methods that expose said APIs It also might benefit us to look into adding the feature discussed here - https://github.com/GoogleCloudPlatform/gcloud-common/issues/80 |
For now at least, I think linking to proto files is sufficient. |
Cc: @omaray We want the documentation for GAX (i.e. LanguageServiceApi). The generated files are more language-idiomatic and serve methods with additional features such as parameter-flattening / page-streaming, that are not seen in the proto files. We will also add auto-generated usage samples to individual method. |
Correct. We want the documentation of GAPIC/GAX to show. Not every API will have a handwritten layer (or at least at the beginning). So we want to show the docs of the auto-gen too. |
Just tagging as these are related: https://github.com/GoogleCloudPlatform/gcloud-common/issues/207 |
@stephenplusplus Looks amazing! We finally did it!! Really appreciate your great work!!! |
Opening an issue to track discussion on how we should go about documenting GAX from within our library.
The text was updated successfully, but these errors were encountered: