Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Feature request: significant figures
See original GitHub issueThis was requested in #117, which was closed by #127 that provides padding instead of significant figures.
Significant figures are useful. Let’s say you want to see 1.34GB instead of 1GB but don’t want to see 724.16MB instead of 724MB.
For instance, GitHub Releases is using significant figures:
I open this issue because #117 is closed. A new issue is good for tracking its status and making potential contributors aware of it.
https://github.com/avoidwork/filesize.js/issues/117#issuecomment-863161844
I know we need a PR or there won’t be this feature, so I’m not requesting the maintainer to provide this feature 😃
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The implementatiomn doesn’t seem to be working at all.
Thanks for implementing this. I’m now using the precision option alone and it works fine.