Display byte units in text list/get output#1265
Open
nanookclaw wants to merge 1 commit into
Open
Conversation
fkorotkov-oai
approved these changes
Jun 17, 2026
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.
Updates the text render paths for
tart listandtart getso theirDiskandSizevalues are shown withByteCountFormatterhuman-readable units, while preserving the existing field and column names.The JSON paths keep their previous machine-readable behavior for compatibility:
tart list --format jsonstill emits integer GB values forDiskandSize, andtart get --format jsonstill emits integer GB forDiskplus the existing three-decimal GB string forSize.Focused tests cover both compatibility shapes and the human-readable text projections.
Fixes #820
Testing
git diff --checkswift test --filter 'GetTests|ListTests'(swiftis not installed in this environment)