Refactor: standardize memory byte formatting across the codebase#37
Merged
Merged
Conversation
SickleFire
approved these changes
Jun 9, 2026
SickleFire
left a comment
SickleFire
left a comment
Owner
There was a problem hiding this comment.
The code looks great. The logic is clean, and using f64 constants for the byte conversions is a good approach.
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.
fixes #34
I created a centralized utility module at {src/utils/formatting.rs}. It includes a {format_bytes(size: u64) -> String} function that automatically scales the size to the appropriate base-2 unit (B, KB, MB, GB, TB) and formats it consistently to two decimal places.