"Fossies" - the Fresh Open Source Software Archive
Member "Atom/resources/app/apm/node_modules/gauge/CHANGELOG.md" (17 Oct 2016, 5436 Bytes) of archive /windows/misc/atom-windows.zip:
As a special service "Fossies" has tried to format the requested source page into HTML format (assuming markdown format).
Alternatively you can here view
the uninterpreted source code file.
A member file download can also be achieved by clicking within a package contents listing on the according byte size field.
- Bug fix: Don’t run the code associated with
disable if the gauge
is already enabled or disabled respectively. This prevents leaking event
listeners, amongst other weirdness.
- New feature: Template items can have default values that will be used if no
value was otherwise passed in.
- Default to
enabled only if we have a tty. Users can always override
this by passing in the
enabled option explicitly or by calling calling
- Update to
email@example.com, which fixes a compatibility bug with the
- #39 Fix tests on 0.10 and add
a missing devDependency. (@helloyou2012)
- Add way to programmatically fetch a list of theme names in a themeset
- Add support for setting themesets on existing gauge objects.
- Add post-IO callback to
gauge.hide() as it is somtetimes necessary when
your terminal is interleaving output from multiple filehandles (ie, stdout
- Fix a refactor bug in setTheme where it wasn’t accepting the various types
of args it should.
- Add setTemplate & setTheme back in.
- Add support for named themes, you can now ask for things like ‘colorASCII’
and ‘brailleSpinner’. Of course, you can still pass in theme objects.
Additionally you can now pass in an object with
platform keys in order to override our guesses as to those values when
selecting a default theme from the themeset.
- Make the output stream optional (it defaults to
setWriteTo(stream[, tty]) to change the output stream and,
BUG FIXES & REFACTORING
- Abort the display phase early if we’re supposed to be hidden and we are.
- Stop printing a bunch of spaces at the end of lines, since we’re already
using an erase-to-end-of-line code anyway.
- The unicode themes were missing the subsection separator.
- All new themes API– reference themes by name and pass in custom themes and
themesets (themesets get platform support autodetection done on them to
select the best theme). Theme mixins let you add features to all existing
- Much, much improved test coverage.
- Got rid of ░ in the default platform, noUnicode, hasColor theme. Thanks
to @yongtw123 for pointing out this had snuck in.
- Fiddled with the demo output to make it easier to see the spinner spin. Also
added prints before each platforms test output.
- I forgot to include
signal-exit in our deps. <.< Thank you @KenanY for
finding this. Then I was lazy and made a new commit instead of using his
PR. Again, thank you for your patience @KenenY.
- Drastically speed up travis testing.
(and testing them on diff platforms).
- Change: The subsection separator from ⁄ and / (different chars) to >.
- Fix crasher: A show or pulse without a label would cause the template renderer
to complain about a missing value.
- New feature: Add the ability to disable the clean-up-on-exit behavior.
Not something I expect to be widely desirable, but important if you have
multiple distinct gauge instances in your app.
- Use our own color support detection.
has-color module proved too magic for my needs, making assumptions
as to which stream we write to and reading command line arguments.
This is a major rewrite of the internals. Externally there are fewer
- On node>0.8 gauge object now prints updates at a fixed rate. This means
that when you call
show it may wate up to
updateInterval ms before it
actually prints an update. You override this behavior with the
- The gauge object now keeps the cursor hidden as long as it’s enabled and
- The constructor’s arguments have changed, now it takes a mandatory output
stream and an optional options object. The stream no longer needs to be
ansiified stream, although it can be if you want (but we won’t make
use of its special features).
- Previously the gauge was disabled by default if
process.stdout wasn’t a
tty. Now it always defaults to enabled. If you want the previous
behavior set the
enabled option to
- The constructor’s options have changed– see the docs for details.
- Themes are entirely different. If you were using a custom theme, or
referring to one directly (eg via
you’ll need to change your code. You can get the equivalent of the latter
var themes = require('gauge/themes')
var unicodeTheme = themes(true, true) // returns the color unicode theme for your platform
The default themes no longer use any ambiguous width characters, so even
if you choose to display those as wide your progress bar should still
- Templates are entirely different and if you were using a custom one, you
should consult the documentation to learn how to recreate it. If you were
using the default, be aware that it has changed and the result looks quite
a bit different.