feat(google/cloud/bigquery/storage/v1): onboard a new library#8861
feat(google/cloud/bigquery/storage/v1): onboard a new library#8861quirogas wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
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.
| nodejs: | ||
| package_name: '@google-cloud/bigquery-storage-api' |
There was a problem hiding this comment.
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 APIReferences
- To override the metadata name and pretty name for a library to avoid naming conflicts, configure
metadata_name_overrideandname_pretty_overrideinlibrarian.yamlinstead of manually editing the generated.repo-metadata.jsonfile.
No description provided.