chore: librarian generate pull request: 20251107T114237Z#13328
Conversation
Summary of ChangesHello @jskeet, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request primarily consists of an automated update to the Google Cloud Storage client library. The core changes involve substantial improvements to the documentation for numerous API methods, providing clearer explanations of their functionality, detailed IAM permission requirements, and specific behavioral nuances related to bucket and object management. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request, generated by the Librarian CLI, updates the Cloud Client Libraries from protos. The changes primarily consist of updating documentation comments across the storage package to be more descriptive and consistent. This includes adding details about IAM permissions, behavior with soft-deletes, and general wording improvements. My review focuses on the clarity and formatting of these new comments. I've pointed out a couple of typos and several instances of awkward line wrapping in the generated comments that could be improved for better readability. While these are likely from an upstream source, addressing them would improve the overall quality of the documentation.
| @@ -432,26 +432,23 @@ type internalClient interface { | |||
| // | |||
| // API Overview and Naming SyntaxThe Cloud Storage gRPC API allows applications to read and write data through | |||
There was a problem hiding this comment.
There's a missing space between 'Syntax' and 'The', which appears to be a typo.
| // API Overview and Naming SyntaxThe Cloud Storage gRPC API allows applications to read and write data through | |
| // API Overview and Naming Syntax The Cloud Storage gRPC API allows applications to read and write data through |
| // LockBucketRetentionPolicy permanently locks the retention | ||
| // policy that is | ||
| // currently applied to the specified bucket. |
There was a problem hiding this comment.
The line wrapping in this comment is a bit awkward and harms readability. Consider re-wrapping for better flow. This pattern of awkward wrapping appears in several other comments in this file.
| // LockBucketRetentionPolicy permanently locks the retention | |
| // policy that is | |
| // currently applied to the specified bucket. | |
| // LockBucketRetentionPolicy permanently locks the retention policy | |
| // that is currently applied to the specified bucket. |
| @@ -818,26 +967,23 @@ type gRPCClient struct { | |||
| // | |||
| // API Overview and Naming SyntaxThe Cloud Storage gRPC API allows applications to read and write data through | |||
There was a problem hiding this comment.
There's a missing space between 'Syntax' and 'The', which appears to be a typo. This is a recurring issue in this file.
| // API Overview and Naming SyntaxThe Cloud Storage gRPC API allows applications to read and write data through | |
| // API Overview and Naming Syntax The Cloud Storage gRPC API allows applications to read and write data through |
| // Requires `storage.buckets.get` | ||
| // IAM permission on | ||
| // the bucket. Additionally, to return specific bucket metadata, the |
There was a problem hiding this comment.
This comment has some awkward line breaks that affect readability. Consider keeping related parts of the sentence on the same line where possible to improve readability.
| // Requires `storage.buckets.get` | |
| // IAM permission on | |
| // the bucket. Additionally, to return specific bucket metadata, the | |
| // Requires `storage.buckets.get` IAM permission on the bucket. | |
| // Additionally, to return specific bucket metadata, the |
| // Restores a | ||
| // soft-deleted object. |
|
This is intended to unblock the Storage team while we're investigating googleapis/librarian#2821 |
PR created by the Librarian CLI to generate Cloud Client Libraries code from protos.
BEGIN_COMMIT
BEGIN_NESTED_COMMIT
feat: make return_partial_success and unreachable fields public for list Bucket
PiperOrigin-RevId: 828488192
Library-IDs: storage
Source-link: googleapis/googleapis@3a77bd60
END_NESTED_COMMIT
BEGIN_NESTED_COMMIT
docs: updates to docs and docs formatting
PiperOrigin-RevId: 828488192
Library-IDs: storage
Source-link: googleapis/googleapis@3a77bd60
END_NESTED_COMMIT
END_COMMIT
This pull request is generated with proto changes between
googleapis/googleapis@72e7439c
(exclusive) and
googleapis/googleapis@3a77bd60
(inclusive).
Librarian Version: v0.4.1-0.20251107065905-10749bd2f1b8
Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/librarian-go@sha256:313c142a607526975c2313348d975b1efe84e2dd68e768e76354dd3a45577637