Change : to :: for controller method (deprecated for 4.1)

[mazarini]

Suppress deprecated messages and fix a php-cs-fixer message

[stof]

that's dropping support for old older versions of Symfony. That's not something we can do yet.

[BackEndTea]

I have seen other bundles create a separate 4.1+ list of routes. That does mean that as long as versions below 4.1 are supported every update done to those files has to be done twice.

[sharif9876]

@stof do we have to override the routes ourselves then if using 4.1? The deprecation is currently not allowing phpunit to pass for my project

[pscheit]

there is an env var to disable deprecation warnings in phpunit

set SYMFONY_DEPRECATIONS_HELPER
to 0 in your phpunit xml file for example

[Tomsgu]

@stof Would solution of @BackEndTea (#2806 (comment)) be acceptable here or we should wait until 2.8 will be dropped?

[kubk]

This warning makes my development log unreadable because of a lot of deprecation warnings.

@Tomsgu Setting SYMFONY_DEPRECATIONS_HELPER=weak is not acceptable because it only hides the deprecation instead of fixing it.

[kubk]

@stof What do you think about creating separate xml files for Symfony 4.1+? Example: hwi/HWIOAuthBundle#1397

[Tomsgu]

@kubk I don’t know where do you find Symfony_deprecation_helper=weak.

I spoke about different routing files. One for 4.1+ and the other for old versions.

[kubk]

@Tomsgu Sorry, you are right.

Also I agree with you about different routing files, for me it solves the problem.

[XWB]

Fixed in #2853