Added a verbose command line option.
#89
Conversation
In order to improve the signal to noise ratio of shifter, I added a `verbose` option to print `[info]` and `[queue]` messages. With this option, which defaults to false, those messages are no longer printed.
| @@ -2,7 +2,7 @@ | |||
| "name": "shifter", | |||
| "description": "New YUI build tool based on Gearjs, so let's shift some gears", | |||
| "author": "Dav Glass <[email protected]>", | |||
| "version": "0.4.1", | |||
| "version": "0.4.2", | |||
There was a problem hiding this comment.
This is a great pull, except for this change. Generally speaking, the version number should never be touched in a pull request. It'll be modified by the maintainer when they decide to publish a release.
There was a problem hiding this comment.
Sorry, I didn't realize that. I changed it so I could install it myself and try it out, then, not knowing any better, I just left it behind.
There was a problem hiding this comment.
No worries, just pointing it out. :)
Locally, npm link in the root of the package should be sufficient to test, no need to modify the version string.
On Jun 26, 2013, at 12:12 PM, Satyam wrote:
In package.json:
@@ -2,7 +2,7 @@
"name": "shifter",
"description": "New YUI build tool based on Gearjs, so let's shift some gears",
"author": "Dav Glass [email protected]",
- "version": "0.4.1",
- "version": "0.4.2",
Sorry, I didn't realize that. I changed it so I could install it myself and try it out, then, not knowing any better, I just left it behind.—
Reply to this email directly or view it on GitHub.
In order to improve the signal to noise ratio of shifter,I added a
verboseoption to print[info]and[queue]messages.
With this option, which defaults to false, those messages are no longer printed.
I felt those message were more useful to debug shifter itself than to those using shifter.
With less clutter on the report, the errors and warnings stand out much more.