- 19 Nov, 2014 1 commit
-
-
Matt Bell authored
-
- 18 Nov, 2014 10 commits
- 17 Nov, 2014 1 commit
-
-
Matt Bell authored
-
- 14 Nov, 2014 22 commits
-
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Brian Tiger Chow authored
License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
-
Brian Tiger Chow authored
@mappum License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
-
Matt Bell authored
-
Matt Bell authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
Attention @maybebtc @mappum I cleaned up + simplified the main flow. Now, all printing is contained inside main itself! (:cheer:). I do this with the help of a cmdInvocation struct that has both a Parse and Run. The only major clunkiness left is that the "CallCommand" is still its own function. But *shrug*. Please test it works as we would expect. i changed much of the flow, so likely that i missed a complicated edge case. main roadmap: - parse the commandline to get a cmdInvocation - if user requests, help, print it and exit. - run the command invocation - output the response - if anything fails, print error, maybe with help
-
Matt Bell authored
-
Brian Tiger Chow authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
commands: Ensure argument parsing maintains total argument count, so that argument validation will fail if there are too many
-
Matt Bell authored
-
- 04 Nov, 2014 6 commits