-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Introduce dedicated logger channel for deprecations #13642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
1e91b18
to
c257763
Compare
setup/upgrade_major.rst
Outdated
@@ -120,6 +127,48 @@ done! | |||
|
|||
$ SYMFONY_DEPRECATIONS_HELPER=max[total]=999999 php ./bin/phpunit | |||
|
|||
Deprecations in logs | |||
~~~~~~~~~~~~~~~~~~~~ | |||
If you use the Symfony default configuration, the deprecations are also logged in a ``prod.deprecations.log`` file (prod environment): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
iirc this config is not enabled now by default in the recipe
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes you're right, it's not enabled but present in the recipe as a comment because as a rule of thumb you only need to log deprecations in prod when you plan to migrate to the next major. IMHO it may be considered as the default configuration even if it's not always enabled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Understood, but maybe rewrote mentioning that this need to be enable, as by default config, it is not the case, and one can understood it is and then never find this file :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yes sorry; I didn't make attention that the problem was in this section, thank you 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated 🙂
c257763
to
d647d6e
Compare
Please review symfony/recipes#775 and update this PR accordingly if it looks good to you. |
d647d6e
to
e4a78d9
Compare
Laurent, thanks for this contribution. However, we're closing it as "won't merge". Why? The feature that you created is nice ... but the nicest thing of it is its great discoverability. The needed config comes automatically via Flex (for new projects or those force-updating their recipes) and the new file is easily spot in the var/logs/ directory of the application, so I don't think we need to explain this explicitly to users. Thanks for understanding! |
@javiereguiluz No problem, I understand 🙂 |
Close #13631