Stuck on an issue?

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.

Global log disable

See original GitHub issue

Is your feature request related to a problem? Please describe. I’m incorporating signale into a project, and could not find an easy way to configure signale to be globally disabled in tests, across all files and scopes.

Describe the solution you’d like

signale.config({
    disable: process.env.NODE_ENV === 'test'
})

Please let me know if there’s a way to do this already and whether I can start working on this. Thanks!

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:5 (3 by maintainers)

Top GitHub Comments

4reactions

klaudiosinanicommented, Jun 10, 2018

Nice! Once the feature is added, it will be super easy to utilize it, as it will be reduced to just a single option;

signale.config({disable: true});
// and maybe
signale.disable();
signale.enable();

just as you initially described. This will be the last addition before we hit 1.2.0 : )

0reactions

rsifycommented, Jun 10, 2018

Sweet, looking forward to it!

On 10 Jun 2018, at 17:07, Klaus Sinani notifications@github.com wrote:

Nice! Once the feature is added, it will be super easy to utilize it, as it will be reduced to just a single option;

signale.config({disable: true}); just as you initially described. This will be the last addition before we hit 1.2.0 : )

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/klauscfhq/signale/issues/41#issuecomment-396056377, or mute the thread https://github.com/notifications/unsubscribe-auth/AGw1DzChWcgUJXd59_tfR0qX8wnUlk4gks5t7TY3gaJpZM4UhtAi.