Open robob4him opened 8 years ago
@robob4him Can you link to a specific page and heading where you see this occurring, please?
@weierophinney, np.
https://zendframework.github.io/zend-servicemanager/configuring-the-service-manager/ It's the example after the text:
Alternatively, the above code can be replaced by a factory class instead of a closure. This leads to more readable code. For instance:
Uhm, thats all right by the way. There is no specific namespace given and since the new FactoryInterface
is located under Zend\ServiceManager\Factory\FactoryInterface
, there is no requirement for implementing the old Zend\ServiceManager\FactoryInterface
which defined the createService
method.
But yes, the lack of the use statement in the top of the snippet might lead to the wrong Interface tho.
This repository has been closed and moved to laminas/laminas-servicemanager; a new issue has been opened at https://github.com/laminas/laminas-servicemanager/issues/23.
The documentation states that a factory stored in a class would implement FactoryInterface but it doesn't reference which one. In ZF3 there still exists the ZF2 FactoryInterface which requires a 'createService' method while the ZF3 interface requires '__invoke'.
It is confusing to still have the ZF2 implementation out there when the clear direction in the docs in ZF3. Perhaps it should be removed?