feat: format token usage with "compact" notation #238
Merged
Conversation
This file contains 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
davolokh
approved these changes
Jan 31, 2025
Pull Request Test Coverage Report for Build 13069650094Details
💛 - Coveralls |
peppescg
approved these changes
Jan 31, 2025
alex-mcgovern
deleted the
feat--format-token-usage-with-"compact"-notation
branch
|
Adding comers would help readability (eg 11,928). Maybe for the sake of space, it could be 11k, 1.2m. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Uses compact notation when displaying token usage, so the numbers don't become hard to parse/work with in the UI.