-
Notifications
You must be signed in to change notification settings - Fork 51
Attaching to HAL plugin event manager causes apigility admin to fail to load existing API's #79
Comments
I also have the same problem. |
Same problem here. Instead of $app = $e->getTarget();
$services = $app->getServiceManager();
$helpers = $services->get('ViewHelperManager');
$hal = $helpers->get('Hal');
$hal->getEventManager()->attach('renderEntity', array($this, 'onRenderEntity')); use $app = $e->getTarget();
$services = $app->getServiceManager();
$sharedEvents = $services->get('SharedEventManager');
$sharedEvents->attach('ZF\Hal\Plugin\Hal', 'renderEntity', array($this, 'onRenderEntity')); (from https://groups.google.com/a/zend.com/forum/#!msg/apigility-users/p4nm3scFxJM/D9ZjUqECYWUJ) |
Using the SharedEventManager in the way described by @gaco79 from the Google Groups thread fixed the problem resulting in the error message: Missing parameter "name" ++ for solution. |
+1 for solution |
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#58. |
After attaching a listener to HAL plugin event manager and trying to edit API's in /apigility/ui#/api,and clicking on an existing API, it wont load. When I comment out the onBootstrap() method in Module.php, the existing API's load normally.
The call to /apigility/api/module/FileApi/rest?version=1 fails with this response:
The text was updated successfully, but these errors were encountered: