Skip to content
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

Updated default option handling for CLI #496

Merged
merged 1 commit into from
Feb 3, 2015

Conversation

oojacoboo
Copy link
Contributor

The defaults were overriding settings specified for colorize and timestamp. I added a check to see if it's been set, otherwise, default.

The defaults were overriding settings specified for colorize and timestamp.  I added a check to see if it's been set, otherwise, default.
@oojacoboo
Copy link
Contributor Author

So, I believe the issue revolves around calling cli() after constructing the transport

@oojacoboo
Copy link
Contributor Author

This does become a non-issue if you don't call .cli() after constructing your transport. I have since moved it to the default winston object where I was previously having issues and needing to call again. If this change doesn't cause any other known issues, I'd still recommend it though. Thanks!

@indexzero
Copy link
Member

👍 but we need tests.

indexzero added a commit that referenced this pull request Feb 3, 2015
Updated default option handling for CLI
@indexzero indexzero merged commit 359c524 into winstonjs:master Feb 3, 2015
@indexzero indexzero mentioned this pull request Feb 3, 2015
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants