Skip to content

feat(google/cloud/bigquery/storage/v1): onboard a new library#8861

Draft
quirogas wants to merge 1 commit into
googleapis:mainfrom
quirogas:feat/onboard-bigquery-storage-api
Draft

feat(google/cloud/bigquery/storage/v1): onboard a new library#8861
quirogas wants to merge 1 commit into
googleapis:mainfrom
quirogas:feat/onboard-bigquery-storage-api

Conversation

@quirogas

Copy link
Copy Markdown
Contributor

No description provided.

@quirogas quirogas self-assigned this Jul 10, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new auto-generated Node.js client library, @google-cloud/bigquery-storage-api, complete with configuration files, TypeScript/JavaScript source code, unit and system tests, and protocol buffer definitions for the BigQuery Storage API. Feedback suggests configuring metadata_name_override and name_pretty_override under the nodejs section in librarian.yaml to avoid naming conflicts with the existing google-cloud-bigquery-storage library and to fix broken auto-generated links in the README.md.

Comment thread librarian.yaml
Comment on lines +544 to +545
nodejs:
package_name: '@google-cloud/bigquery-storage-api'

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

To avoid naming conflicts with the existing google-cloud-bigquery-storage library (which already uses the metadata name bigquerystorage and pretty name BigQuery Storage), please configure metadata_name_override and name_pretty_override in librarian.yaml under the nodejs section. This will also fix the auto-generated documentation and repository links in the README.md which currently incorrectly point to google-cloud-bigquery-storage instead of google-cloud-bigquery-storage-api.

    nodejs:
      package_name: '@google-cloud/bigquery-storage-api'
      metadata_name_override: bigquerystorage-api
      name_pretty_override: BigQuery Storage API
References
  1. To override the metadata name and pretty name for a library to avoid naming conflicts, configure metadata_name_override and name_pretty_override in librarian.yaml instead of manually editing the generated .repo-metadata.json file.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant