Issue Type: Bug Created: 2011-12-20T13:52:14.000+0000 Last Updated: 2011-12-23T01:03:49.000+0000 Status: Resolved Fix version(s): Reporter: Jeroen de Lau (jeroen.delau) Assignee: Evan Coury (evan.pro) Tags: - zend\module
Related issues: Attachments:
ZendFramework Beta 1 Zend\Module\Manager line 97-98 Documentatio: http://packages.zendframework.com/docs/latest/…
This is either a coding or documentation issue.
On these lines the loadModule.resolve is loaded, which by default is picked up by the ModuleResolverListers. The callback seems to indicate that the execution should stop after a listener has returned a class. In that case it should use triggerUntil.
However, since the trigger method in Zend\EventManager\EventManager also has a fourth callback parameter it might be that instead the documentation needs to be updated.
Posted by Evan Coury (evan.pro) on 2011-12-21T22:01:11.000+0000
This is, indeed, a documentation issue. The trigger() method was updated to accept a callback as the optional 4th parameter, giving it all of the functionality of triggerUntil(). It appears the docs have not yet been updated to reflect this.
Posted by Evan Coury (evan.pro) on 2011-12-21T22:40:20.000+0000
Fixed with PR 681: https://github.com/zendframework/zf2/pull/681
Posted by Evan Coury (evan.pro) on 2011-12-23T01:03:49.000+0000
Fixed with PR 681 which is now merged.
Have you found an issue?
See the Overview section for more details.