Full yargs cli #170
Full yargs cli #170
Conversation
…ne into full-yargs-cli
|
@lilleyse Could you look at this when you get a chance? |
| return; | ||
| } | ||
| var argv = require('yargs') | ||
| .usage('Usage: $0 -i inputPath -o outputPath') |
There was a problem hiding this comment.
Should the usage and example be like node $0?
|
Using yargs in this way is it possible to allow processing a file without |
|
Looks good, just those comments. |
|
This has been updated as well. 'node' has been added to the usage and help output. Input and output can also be passed implicitly as the first and second unmarked parameters without |
|
Looks nice! @lilleyse OK to merge? |
|
Only issue I'm noticing is it throws an error when no arguments are supplied. Should be a quick fix @lasalvavida and then I'll merge. |
…f-pipeline into full-yargs-cli
so passing it as an option isn't necessary
|
@lilleyse This is updated and merged with master. |
|
@lilleyse Could you look at this when you get a chance? |
|
Ah thanks for the reminder, I did review the latest changes but must have gotten sidetracked. |
Uses yargs to fully establish default settings, types, etc. Makes the command line
-hflag a lot more useful, and easier to maintain.