feat: add setLogger for custom logger support #96
+201
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Attempts to address #84
This PR adds a
setLogger()function that allows users to provide a custom logger implementation. This is a simpler implementation but follows the general pattern used by OpenTelemetry and other JS libraries.This enables:
Changes
setLogger(customLogger: Logger | null)to set a custom logger or disable logginggetLogger()to retrieve the current logger instanceNoOpLoggerclass for when logging is disabledloggerimport still worksUsage Examples
Disable logging entirely:
Plain logger without ANSI colors (for GCP/cloud):
Use Winston for structured JSON logging:
Test Plan
npx vitest run core/test/utils/logger_test.ts