Handling reset() function w/o argument

[webdiscus]

Hello @panoply,

what do you think about reset() function?
I know we can do without it, but in very rare cases it could be useful. Here are usage cases on GitHub.

The reset ANSI code doesn't have open/close codes, only single code ESC[0m.

Currently behaviour

This doesn't make sense:

ansis.reset(); // empty string '', w/o ESC[0m
ansis.reset(''); // empty string '', w/o ESC[0m
ansis.reset('Text'); // ESC[0mTextESC[0m

For example:

console.log(ansis.red('red ' + ansis.underline('underline') + ' text'));

Output:

My be it is a poor example, but if we want reset red color for underline and following text, e.g.:

console.log(ansis.red('red ' + ansis.reset.underline('underline') + ' text'));

Output:

It would reasonable to use the reset() function instead of string wrapping:

console.log(ansis.red('red ' + ansis.reset() + ansis.underline('underline') + ' text'));

Idea

The reset() function without arguments should return ESC[0m to reset the previous styles.

This is the only case where handling of an absent argument makes sense, because all other functions must have an argument.

[panoply]

Hey,

I actually have couple of use cases where this would indeed come in handy. I also very much like the approach of eliminating the chaining and using in isolation. In the CLI I am building where I use ansis heavily for the TUI logic, I can see my using ansis.reset() at various points.

+1 on this

[webdiscus]

Thank you for the feedback.

In a next release I will add the new behaviour:

ansis.reset(); // => ESC[0m

[webdiscus]

@panoply

in v3.10.0 ansis.reset() returns the reset escape code \e[0m

Here is the comparation of handling input arguments in various libraries.

[panoply]

Perfect. It's logical and aligns with expectation.