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
{{ message }}
This repository was archived by the owner on May 4, 2024. It is now read-only.
Soo, any time I use it outside npmlog (which pulses on loglines only), I'm inevitably confused why just calling gauge.show on changes doesn't make the spinner spin.
I'm now of the opinion that gauge.show should increment the spinner just the way pulse does. This would make the two commands essentially identical, just having different short-cut type arguments– show being section and completed, and pulse be subsection. It might be time to just eliminate pulse entirely.
The text was updated successfully, but these errors were encountered:
Just started using gauge for the first time -- excellent work, btw -- and I agree with this. I wrote a short test app and was surprised the spinner didn't change, then immediately tried adding the pulse call to each show call and saw the results I wanted.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Soo, any time I use it outside npmlog (which pulses on loglines only), I'm inevitably confused why just calling
gauge.show
on changes doesn't make the spinner spin.I'm now of the opinion that
gauge.show
should increment the spinner just the way pulse does. This would make the two commands essentially identical, just having different short-cut type arguments–show
beingsection
andcompleted
, andpulse
besubsection
. It might be time to just eliminatepulse
entirely.The text was updated successfully, but these errors were encountered: