Add configurable log levels in CLI and API#29
Merged
Conversation
ryukzak
requested changes
Nov 24, 2025
octoshikari
force-pushed
the
feat/logger-log-level
branch
2 times, most recently
from
1676d2b to
bc974f3
Compare
- Introduced `--log-level` option in CLI for granular logging control. - Enhanced `CodegenLogger` to support log levels (DEBUG, INFO, WARN, ERROR, SILENT). - Updated APIBuilder to allow log level configuration.
octoshikari
force-pushed
the
feat/logger-log-level
branch
from
bc974f3 to
ccd72e9
Compare
Collaborator
Author
|
@ryukzak Review again please, when you will have time for it |
ryukzak
approved these changes
Dec 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
--log-leveloption in CLI for granular logging control.CodegenLoggerto support log levels (DEBUG, INFO, WARN, ERROR, SILENT).