-
-
Notifications
You must be signed in to change notification settings - Fork 495
Update conf to log deprecations in a dedicated channel #775
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
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.
Pull request passes validation.
symfony/framework-bundle/5.1/config/packages/prod/deprecations.yaml
Outdated
Show resolved
Hide resolved
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.
LGTM :)
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.
Pull request passes validation.
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.
Pull request passes validation.
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.
Pull request passes validation.
Config provided by flex - symfony/recipes@daca38d - symfony/recipes#775
Similar to one provided by flex for 5.1 - symfony/recipes@daca38d - symfony/recipes#775
What effect does this have on Symfony versions prior to 5.1, such as LTS 4.4? |
There is no effect for versions before 5.1. If you enable the configuration to log deprecation in a separate file for these versions, the file should stay empty since nothing is sent to the |
That makes sense for the new (commented out) code, but what about the code that was removed as part of this PR? If I want to log deprecations in 4.4, is it advised that I keep that intact? |
Yes, you can keep the old code, it will work in 4.4 and also in next versions. Anyway the recipe update should not be proposed in 4.4. |
OK, thanks.
Does that mean there's a bug? Because it is being proposed in 4.4. (My dependency is defined as |
Oh indeed, good catch !
Do you want to create a PR for fixing it ? I would do it otherwise. |
@l-vo It's all yours. |
Follows symfony/symfony#36621