ZF-6125: Zend_Tool_Framework_Manifest_Repository getMetadata() should use either client or non client naming (not both)

Issue Type: Improvement Created: 2009-03-25T08:13:38.000+0000 Last Updated: 2009-04-24T11:17:29.000+0000 Status: Resolved Fix version(s): - 1.8.0 (30/Apr/09)

Reporter: Maik Kreutzfeldt (grayfellow) Assignee: Ralph Schindler (ralph) Tags: - Zend_Tool

Related issues: Attachments:


Concerning SVN standard/incubator:

The problem occured when requesting manifest data for a custom method listing

<pre class="highlight">
$searchParams = array(
            'name'  => 'cliProviderName',
            'type'  => 'Provider',
            'value' => 'some-class',


$searchParams = array(
           'name'                 => 'cliActionableMethodLongParameters',
            'type'                  => 'Provider',
            'providerName'  =>    'SomeClass'
            'actionName'    =>     'Action',
            'specialtyName' =>    '_Default',

Changing the providerName did return null in both cases.


Posted by Ralph Schindler (ralph) on 2009-04-24T11:17:28.000+0000

The Console Client manifest has been updated since this report.

THe general idea here is that the console client is adding information to the registry that it (and others) can use to determine what the client naming is.

Specifically, the argument parser and help system use these values to determine both what to dispatch and how to present help to the user.

If you have other concerns or questions, lets discuss on the mailing list as this is good feedback!


Have you found an issue?

See the Overview section for more details.


© 2006-2018 by Zend, a Rogue Wave Company. Made with by awesome contributors.

This website is built using zend-expressive and it runs on PHP 7.