chore: update byte units on frontend#4444
Conversation
|
🚅 Deployed to the rivet-pr-4444 environment in rivet-frontend
|
PR Review: chore: update byte units on frontendThis PR updates byte unit labels throughout the billing frontend from decimal (KB/MB/GB/TB) to binary (KiB/MiB/GiB/TiB) IEC units, and switches the Behavioral change (not just a label fix)The old code used decimal constants: const KB = 1_000n
const GB = 1_000_000_000n
const TB = 1_000_000_000_000nThe new code uses binary math via bigBytes.KiB(4n) = 4096n // was 4000n (+2.4%)
bigBytes.GiB(5n) = 5,368,709,120n // was 5,000,000,000n (+7.4%)
bigBytes.TiB(1n) = ~1.1T // was 1,000,000,000,000n (+9.9%)This changes the numeric thresholds used for billing calculations (free/pro/team plan allowances), not just the display labels. Please confirm the backend enforces limits using the same binary convention — if the backend uses
|
f1b6d0a to
d4011f0
Compare
5b2bead to
cfc4fad
Compare
d4011f0 to
3b845cb
Compare
cfc4fad to
65280b5
Compare
65280b5 to
84dbf32
Compare
3b845cb to
1028b2c
Compare
84dbf32 to
90c2e97
Compare
1028b2c to
88d15c3
Compare
88d15c3 to
ede07de
Compare
90c2e97 to
ebdaa13
Compare
ede07de to
e9536ed
Compare
63b3a1f to
73107a6
Compare
e9536ed to
cf68e1c
Compare
1cb5f34 to
34988dd
Compare
791a38d to
d5c2eee
Compare
34988dd to
388ad2e
Compare
d5c2eee to
5572d7e
Compare
388ad2e to
b1b526d
Compare
b1b526d to
6ab46b0
Compare
98fbf07 to
fecf384
Compare
6ab46b0 to
a7a6cca
Compare
a7a6cca to
3aae0b5
Compare
fecf384 to
0277ea1
Compare
Merge activity
|
3aae0b5 to
98387ac
Compare

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context.
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist: