-
Notifications
You must be signed in to change notification settings - Fork 11
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
Improve validation of command-line options #203
Comments
👍 |
I've integrated the Commando component (linked above) into
We get aliases, so that And, most importantly, we get option validation, so that
instead of running without a limit. Also, the value of Only drawback I can see is that Commando doesn't support the |
To test, switch to the issue-203 branch, then run
to composer.json. |
AFAICT, only README.md and the tutorial (including screenshots) would need to be updated to reflect the change in command-line syntax. |
@mjordan Thanks. I will schedule some time to test. |
Excellent thanks. Just did a smoke test on Windows and everything appears to work as expected. |
@mjordan Passed my initial basic tests. |
As discussed offline, I've tested this pretty thoroughly so I'll merge into master. |
Merged with 72b5d88; reopening because updating tutorial is yet to be done. |
Tutorial has been updated to show no |
Currently, there is little feedback from MIK if the user misspells an .ini file, or worse, misspells 'limit' (in which case MIK starts up and doesn't apply a limit).
We could perform better option validation, or incorporate a CLI library like https://github.com/nategood/commando/ that does this automatically. We'd want a CLI library that didn't interfere with our class loading or other code-level logic. We should check out the Symfony Console Component but I wouldn't want us to be forced to adopt the entire Symfony ecosystem. It's awesome but overkill for MIK.
The text was updated successfully, but these errors were encountered: