You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, library gives no control to how :rate is actually formatted. It's pretty standard use case (it's actually used in the README) when bytes are used for total and tick values. However, the library would output rate in plain bytes, which is absolutely unpractical for end users.
I would suggest to introduce a rate formatter function, e.g.:
This is a gravely needed feature. Every now and then I come across a need to display download progress, and I have to copy & paste some boilerplate to add faux tokens to my progress bar:
@NathanPB's version definitely provides an elegant way to specify these formatters and even includes a library of standard formatters. It is a bit more verbose though for the "regular" tokens and also it cannot be used as a drop-in replacement for progress in other contexts.
Hello!
Thank you for this great library!
Right now, library gives no control to how
:rate
is actually formatted. It's pretty standard use case (it's actually used in the README) when bytes are used for total and tick values. However, the library would output rate in plain bytes, which is absolutely unpractical for end users.I would suggest to introduce a rate formatter function, e.g.:
This will output byte rate in a user-friendly fashion, e.g.:
1.56 MB/sec
.Thanks!
The text was updated successfully, but these errors were encountered: