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
Drop support for Symfony 4 #1586
Conversation
5f3a918
to
94a4fa8
Compare
94a4fa8
to
60a26f8
Compare
I think we should then also remove all of those? https://github.com/doctrine/DoctrineBundle/blob/2.8.x/Resources/config/dbal.xml#L26-L37 This would then also fix #1585 |
There are tests in place that assert that the |
People will be upset about removing this service for sure, but better to throw it in their face that they need to change something, rather than their code not doing anything. So I agree with removal. |
Symfony supports marking a service as deprecated. That's what we should do for the logger service when we use the middleware |
But with this PR we will always use the middlewares. So the legacy logging services are not doing anything anymore. You would prefer to still keep them and deprecate them? EDIT: I personally would be fine with removing them. I see those as internal details and not as an extension point that one should rely on. |
Active support for Symfony 4 ends this month. This PR drops compat code we have maintained for Symfony 4.