Repository navigation
Move charmbracelet/log to Command Line and drop the Logging category - #84
Merged
Merged
Conversation
Its distinguishing features are colorful, styled terminal output, which is what CLI tools want; the standard library's slog is the logger otherwise. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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.
charmbracelet/log is about presentation: levels with colours, styled prefixes and key-value pairs that read well in a terminal. That is what CLI tools want, so it moves to Command Line next to Bubble Tea. With it gone, Logging is empty and is removed from
list.json; the standard library's slog is the logger otherwise, and the category returns if a logger earns a place later.🤖 Generated with Claude Code