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 Feb 6, 2020. It is now read-only.
I find the new Config Abstract Factory very handy. That saves a lot of typing. So thanks for that 👏.
One thing that keeps bothering me however is that there seems to be only a single configuration array that determinates how services in all service manager are to be instantiated. You can mix plain services, controllers and view helpers!
IMO that:
Introduces some possible problems if service names are identical.
Disallows one to properly split the configuration per service manager. When you have a lot of services it really helps to categorize them.
Another way of tackling this would be to add the config key directly as one of the components of the service manager config. But there are obviously other options.
I find the new Config Abstract Factory very handy. That saves a lot of typing. So thanks for that 👏.
One thing that keeps bothering me however is that there seems to be only a single configuration array that determinates how services in all service manager are to be instantiated. You can mix plain services, controllers and view helpers!
IMO that:
Another way of tackling this would be to add the config key directly as one of the components of the service manager config. But there are obviously other options.
return [ 'factories => [], \Zend\ServiceManager\AbstractFactory\ConfigAbstractFactory::class => [] ];
I am curious what other people think; or how they tackle this problem?
The text was updated successfully, but these errors were encountered: