Symplify: Symfony\Component\Debug\Exception\ContextErrorException in ControllerFinder.php line 30:

[scion4581]

Hi! How it gonna work if we have trying concatenate array with string?

https://github.com/DeprecatedPackages/ControllerAutowire/blob/0b188bf7db81d9a23e2a1ce12ff3c5edb2dab42b/src/HttpKernel/Controller/ControllerFinder.php#L30

[TomasVotruba]

Hey, that package is not maintained anymore. Feel free to take it over and fix it

[scion4581]

Sure I will, but interesting how it was working before...
Anyway,big thanks for such functionality for symfony 2.8 <= versions < 3.4

[TomasVotruba]

It was must have :) I'm glad it helps you.

Why not upgrade to Symfony 3.3? It has awesome features that package is not covering: https://www.tomasvotruba.cz/blog/2017/05/07/how-to-refactor-to-new-dependency-injection-features-in-symfony-3-3/

Rector helps you with all the simple cases: https://github.com/rectorphp/rector

[scion4581]

For myself i was starting with version 3.4 , but now I was asked to do some work on project with 3.2 ,
thats why i was suprised why i cant make controller like service(which in 3.4 default) and extend base sf controller to get work built in futures like render function. and yesterday i figure out that u must make a choice - either extend base controller and get all services via $this->container->get or define controllers like services and inject all u need by hand... Its painful after using 3.4 :)
So all your articles which i was found come in handy, thnx again and now I'm a regular reader of u blog:)

[TomasVotruba]

Yes, it is painful. I work with other PHP framework and this is the single point of failure for architecture designs, leads to registration of big classes only, no decoupling.

Glad you like it :+1: let me know at Rector if you need some migration to Smyfony 3.4 that is missing.
We got $this->get() case covered as well