O hai! :)
I started to play around with the idea of a Cli module/component/whatever.
Some code:
https://github.com/robertbasic/zf2-cliSo far everything is just stuffed under one namespace, hopefully it'll end
up as something usable :)
The experienced ones among you will notice that the code (the Bootstrap.php
and the Application.php) is just a blatant copy of the code from Zend\Mvc.
I just took out the request/response/routing stuff and (tried to) replaced
it with Zend\Console\Getopt. But hey, it works!
The end idea is to have a CliApplication which can be used for modules that
need command line interaction. These Cli modules _should_ be aware of all
the HttpApplication and the HTTP modules. Why? Because the first Cli module
I want to create will need to be aware of all the "installed" modules :)
Major work I plan to do:
1) Break the current Application::run into Application::run and
Application::dispatch so we can have pre. and post.dispatch events.
2) Wrap the action dispatching in to a try/catch block so any exception
thrown from inside the action (or deeper) will be caught and nicely output
to the console (see 4))
3) Make the "cli" controllers similar to the current ActionControllers, e.g.
make them locator aware and dispatchable. Also, to have a
(set|get)ConsoleOptions available to all the cli controllers, so any command
line arguments/flags/options can be accessed from inside the action.
4) Create some kind of a "response", something that will implement
Zend\Stdlib\MessageDescription down the line, so it can be sent to STDOUT
normally (print it, pipe it to some other process...). Bonus points for
making it print with colours! Green for all good, red for errors, stuff like
that. Maybe we have this already?
5) Once 4) is done, implement send() to Cli\Application.
With the current code, running php bin/cli.php --foo-bar will run the
fooBarAction in the Controller\Cli controller.
One thing I'm not sure about is are these cli controllers. I have 3
different ideas for them at the moment:
1) Each Cli module has *one* Controller\Cli (the actual controller name
configurable thanks to Zend\Di, but the _recommended_ name in this case
would be Controller\Cli). All the callable actions are to be implemented in
this controller. Basically, just as it is now:
> php bin/cli.php --foo-bar will run the fooBarAction in the
Controller\Cli controller.
2) Each Cli module has as many controllers as there are callable actions and
the actual action name would be something like executeAction() or similar.
In this case, the action name would not be configurable. Example:
> php bin/cli.php --foo-bar will run the executeAction in the
Controller\FooBar controller.
3) Each Cli module can have as many controllers and actions as the developer
wants. This way would complicate the whole Console\Getopt things because the
calling would be something like:
> php bin/cli.php -c foo -a bar --param value
and this would call the barAction in the Controller\Foo controller, passing
"param" with "value" (note: the param passing stuff would be available in
any case).
Also, I never ever used Zend\Tool (tested it once it came out, said meh, and
forgot about it). If something/anything/everything from above is already in
Zend\Tool, or can be taken out from there or this whole thing can be made
with a simple Zend\Tool provider, speak now :)
Comments? Thoughts? Ideas?
Let the bashing begin :)
Cheers,
Robert
--
~Robert Basic;
http://robertbasic.com/
Locked
