Apigility Admin UI issue

[JiNexus]

Hi Zend Team,

Just a concerned developer reporting some bugs. After I update my vendor via composer (sudo php composer.phar update) I went to my created services and wanted to change the Hydrator Service but the drop down selection of Hydrator Service Name in the admin is not working (it became an input field) and not showing the other options like, Zend\Stdlib|Hydrator\ObjectProperty, Zend\Stdlib|Hydrator\ClassMethods, etc. Though I find a way to manually change the hydrator service by updating the codes in the module.config.php, I just can't sit here and not report this simple bug. :)
By the way I'm currently using apigility 1.3.2

Cheers!

[swos-]

I can second this. Also using 1.3.2. I thought I had configured something incorrectly, or missed a step in the REST Service Tutorial, so I started from scratch, and tried a second time. Same results.

Under the General Settings tab, The Hydrator Service Name is initially populated, but whenever it's selected, the field becomes blank. I pasted Zend\Stdlib\Hydrator\ObjectProperty into the field, but tabbing to another field reverted it to the original value.

[Twister7]

I have the same problem with Apigility 1.3.3

[jaustin-ons]

For what it's worth, I downloaded the 1.3.2 release from https://github.com/zfcampus/zf-apigility-skeleton/releases and it works at the documentation states it should. That is, the drop down menu populates with the list indicated, and it's possible to select the correct Hydrator.

(Once I got all that working I was able to interact with my test API! I'm really looking forward to using Apigility on projects in the future.)

[ImIOImI]

I have this problem as well. I reverted to 1.3.1 and 1.3.2 neither or which fixed my issue. It may be tied to the admin ui.

[ImIOImI]

Just noticed that I can't add validation filters to a field... might be related

[TimoBos]

I had the same issue, it seems apigility 1.3.3 doesn't like zend-hydrator version 1.1.0
After I added "zendframework/zend-hydrator": "1.0.0", in the composer.json it worked for me.

[michalbundyra]

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