This area of development has been left open so that we can better
understand how developers intend how to use it. I notice you have both
client and action specific options available. There are a few questions:
* where and how do you anticipate recieving and utilizing the values
from these provided options?
* Inside the provider?
* If inside the provider, what kind of API would you expect to be
able to interact with to get said values?
If you could, provide some pseudo code to demonstrate how you'd like use
this feature.
-ralph
Christoph Dorn wrote:
I cannot find any documentation or examples on this.
How can I work with options in the Zend_Tool client, action and provider
classes?
For example:
zf --debug_level 10 create -f component --template default TestComponent
where we have client-level, action-level and provider-level options as
simple flags and with values.
Christoph