Skip to content
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.

Unable to select Hydrator Service Name after update to Apigility1.3.2 #122

Open
markheydon opened this issue May 2, 2016 · 2 comments
Open

Comments

@markheydon
Copy link

Hi,

Recently started a new project, and was getting an issue with composer being out of date -- something around zfcampus/zf-apigility-admin-ui needing to be 1.2.3 but locked at 1.2.2. Performed composer update to get latest version(s) and updated ok.

However now I'm on zf-apigility-admin-ui 1.2.3 I'm having the following issue, issue doesn't seem to be in zf-apigility-admin-ui 1.2.2.

Clicking on the Hydrator Service Name drop-down makes the drop-down disappear and be replaced with text field.

beforedropdown

afterdropdown

Anything I enter into the field is ignored on save and seems to go back to ArraySerializable.

Mark

@morrsky
Copy link

morrsky commented Jun 24, 2016

Hi Mark,

it is possible to edit the value manually in file located at <ApiName>\config\module.config.php at config key
/../

'zf-hal'=> array(
    'metadata_map' => array(
        <_ApiName_>\\V1\\Rest\\<_ServiceName_>\\<_ServiceName_>Entity => array(
            'hydrator' => 'Zend\\Hydrator\\ObjectProperty'
        ),
    ),
),

/../

Hydrators availabe in previous versions:

  • Zend\Hydrator\ArraySerializable
  • Zend\Hydrator\ClassMethods
  • Zend\Hydrator\ObjectProperty
  • Zend\Hydrator\Reflection

Problem you decribed appears in AbstractPluginManagerModel.php:55 where

$reflClass = new \ReflectionClass($this->pluginManager);
$reflClass->getProperty('invokableClasses')->getValue($this->pluginManager);

returns an empty array

@weierophinney
Copy link
Member

This repository has been closed and moved to laminas-api-tools/api-tools-skeleton; a new issue has been opened at laminas-api-tools/api-tools-skeleton#12.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants