-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to write logs only to file avoiding print to terminal #47
Comments
We should duplicate the option for when to write logs for file outputs. Also add additional option for those 'never' |
note that there are two different collectors. EDIT: Oh well, i just saw that this is no longer possible after updating to 2.0 since printLogs is not an allowed property anymore. |
@zvaehn What you are saying was not possible in previous versions either. Now we have proper validation on config to prevent you from sending unused config. Also we dont have two collectors. There is only one collector which is in the support install, that collects the logs and later on sends it to the nod js (the plugin install / the printer) where they actually are written to console and file. |
Well, this sounds much more plausible. Thanks for pointing that out. |
Will be comming in next minor release. |
This is a useful feature. Can this be released sooner? |
I am working on it. |
Add option to write logs only to file avoiding print to terminal #47
Two new options coming up in next release that will replace current |
Released in 2.1.0. |
I would like to have all the logs (not just
onFail
) in a file, having all of them printed to terminal looks too spammy. But it seems like print to terminal currently is inevitable. Is it possible to add some config option to print to file only?The text was updated successfully, but these errors were encountered: