You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
I would like to drop those abstract factories in favor of using the related PluginManagers directly.
Since #93 introduces external packages, it will get more and more difficult to attach plugins/storage adapters to the PluginManagers, if not retrieved by the projects ContainerInterface.
Imho, each external package should provide their own factories for their plugins/storage adapters and just inject these to the related PluginManager (e.g. by using delegators? Some feedback would be great).
The original idea of @marc-mabe was to use the Module object to add aliases and factories to the PluginManager but as of zend-config-aggregator or in projects without zend-mvc, this wont work anymore.
I would appreciate to get some feedback on this. @weierophinney
The text was updated successfully, but these errors were encountered:
Hey there,
I would like to drop those abstract factories in favor of using the related
PluginManager
s directly.Since #93 introduces external packages, it will get more and more difficult to attach plugins/storage adapters to the PluginManagers, if not retrieved by the projects
ContainerInterface
.Imho, each external package should provide their own factories for their plugins/storage adapters and just inject these to the related
PluginManager
(e.g. by using delegators? Some feedback would be great).The original idea of @marc-mabe was to use the
Module
object to add aliases and factories to thePluginManager
but as ofzend-config-aggregator
or in projects withoutzend-mvc
, this wont work anymore.I would appreciate to get some feedback on this.
@weierophinney
The text was updated successfully, but these errors were encountered: