Closed c33s closed 2 years ago
Setting appropriate error_level
setting in codeception.yml should help.
settings:
error_level: E_ALL & ~E_STRICT & ~E_DEPRECATED & ~E_USER_DEPRECATED
Documentation: https://codeception.com/docs/04-FunctionalTests#Error-Reporting
as i mostly searched for "disable deprecation notification" in the issues on github and on search engines, maybe adding the wording "remove/silence/disable deprecation warnings" to the doc section could help.
it would be awesome to have a config flag where i enable/disable the deprecation notification. currently the deprecation notifications is very spammy. i am working on a symfony 5.4 project and i get a big deprecation wall everytime. i played around with
SYMFONY_DEPRECATIONS_HELPER
but it somehow has no effect (also it feels quite strange to use env vars for a static value even ifcodeception.yml
exists.in
Subscriber/ErrorHandler.php
i can verify thatSYMFONY_DEPRECATIONS_HELPER
is set todisabled
. in theregisterDeprecationErrorHandler
function the code doesn't pass the if because of the env var but still all notifications. if i changehandleDeprecationError
to simply return i get the desired result.Details
composer show
)