Fails if your controllers init method depends on an injection with 3.3 about zf1-bridge

[mnapoli]

I see what you mean, but just to be clear this is the small BC-break introduced in 3.2 right? (https://github.com/mnapoli/PHP-DI/releases/tag/3.2.0)

It's a shame the constructor calls init, and not the dispatcher.

+1

Another option is to override the init and include an InjectOn call against itself so that the dependencies are there. This would get you away from a custom dispatcher being required. The drawback is you have to get a handle to the DI container in your init call. If you instantiate the DIcontainer in a bootstrap file it's ugly to pass it down, so it may be better to instantiate it in the init itself.

Seems like the best option to me, given also that it's probably how it will end up for ZF2 integration.

What could be possible is offering 2 options:

• keep using the provided Dispatcher (best solution), but dependencies are not injected in init()
• use a base controller class (to be provided by this library) that fetches the dependencies in the constructor if dependencies are needed in init()

[drdamour]

yes, sorry it was 3.2, guess we were on 3.1 before.

[drdamour]

FYI: i found that moving the logic to preDispatch was the way to go. Especially once i learned that you can use _forward in preDispatch. We had so much ugly code to catch and respond with errors in Init that is now being forwarded to the appropriate error controller instead!