Bytes formatter doesn't respect space separation
See original GitHub issueUsing 0.00b
and 0.00 b
gives the same output (notice the space), no space separation with the 2nd one. The formatter is using state.currentAbbreviations()
, but that doesn’t contain the spaced
parameter (and I don’t think you can actually set it.) - it works in tests, however.
Using let options = Object.assign({}, defaultOptions, providedFormat);
with options.spaceSeparated
makes it work.
Sadly I don’t have time to create a PR, but I hope I could help to get it fixed soon.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
python format string thousand separator with spaces
If Python does not respect grouping=True parameter, you can use locale and a workaround (use monetary format): locale.setlocale(locale.LC_ALL, '') locale.
Read more >Does hexdump respect the endianness of its system?
The traditional BSD hexdump utility uses the platform's endianness, so the output you see means your machine is little-endian.
Read more >Making Sense of Hexdump | SUSE Communities
Here's something really simple that just outputs the whole table as space separated single byte values in hexadecimal:
Read more >Encoding | Protocol Buffers - Google Developers
This document describes the protocol buffer wire format, which defines the details of how your message is sent on the wire and how...
Read more >Understanding Bits, Bytes, and Numerical Bases - Tania Rascia
... by sixteen space-separated, two-column, hexadecimal bytes, followed by the same sixteen bytes in %_p format enclosed in '|' characters.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This bug is also visible in the documentation of the v2 API:
Assuming this is now fixed with #411