Skip to content

feat(google/logging/v2): onboard a new library#8863

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

feat(google/logging/v2): onboard a new library#8863
quirogas wants to merge 1 commit into
googleapis:mainfrom
quirogas:feat/onboard-logging-api

Conversation

@quirogas

Copy link
Copy Markdown
Contributor

No description provided.

@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 the new @google-cloud/logging-api package, which contains auto-generated clients, samples, and proto definitions for the Cloud Logging API (including Config, Logging, and Metrics services). The review feedback highlights two issues: first, the auto-generated links in the README point to the wrong package directory and should be corrected upstream in the generator templates; second, the webpack configuration should be updated to use a more generic library name and filename, as the package exports multiple services rather than just ConfigServiceV2.

Comment on lines +106 to +108
[homepage_samples]: https://github.com/googleapis/google-cloud-node/blob/main/packages/google-logging/samples
[homepage_changelog]: https://github.com/googleapis/google-cloud-node/blob/main/packages/google-logging/CHANGELOG.md
[homepage]: https://github.com/googleapis/google-cloud-node/blob/main/packages/google-logging

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.

medium

The auto-generated links at the bottom of the README point to packages/google-logging instead of this package's directory (packages/google-cloud-logging-api). Since this file is auto-generated, please update the generator templates or configuration upstream to ensure the correct package directory is used for these links.

References
  1. Do not manually edit auto-generated files to fix typos or make other changes, as these edits will be overwritten during the next regeneration. Instead, apply the fixes upstream in the generator or templates.

Comment on lines +19 to +22
output: {
library: 'ConfigServiceV2',
filename: './config-service-v2.js',
},

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.

medium

The webpack configuration appears to have been copied from a single-service package and still uses ConfigServiceV2 as the library name and ./config-service-v2.js as the filename. Since this package exports multiple services (ConfigServiceV2, LoggingServiceV2, and MetricsServiceV2), the library name and filename should be updated to be more generic and representative of the entire package (e.g., LoggingApi and ./logging-api.js).

Suggested change
output: {
library: 'ConfigServiceV2',
filename: './config-service-v2.js',
},
output: {
library: 'LoggingApi',
filename: './logging-api.js',
},

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