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
assuming that an application has factories for its listeners, it would be nice to configure them in a central location and to not pollute the service container. any interest?
I would say that your application should consist auf multiple modules so there are not so many listeners within the service container to have another plugin manager created.
Also you could simply use another php file to separate your listeners to an own config file.
true, i do take advantage of separate modules and PHP files. but in the merged config all services are listed and available from the application service container despite my modular separation.
a listener plugin manager would provide only implementations of the listener interface, so we would gain some type-safety as well as a reduction in the overall number of services registered in the main application service container.
hi Team,
assuming that an application has factories for its listeners, it would be nice to configure them in a central location and to not pollute the service container. any interest?
thanks : )
Originally posted by @abacaphiliac at zendframework/zend-eventmanager#59
The text was updated successfully, but these errors were encountered: