-
-
Notifications
You must be signed in to change notification settings - Fork 892
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
Handle deprecations from Symfony 5.1 #3589
Handle deprecations from Symfony 5.1 #3589
Conversation
d2cd906
to
c163d51
Compare
@@ -18,7 +18,6 @@ | |||
<service id="api_platform.operation_method_resolver" class="ApiPlatform\Core\Bridge\Symfony\Routing\OperationMethodResolver" public="false"> | |||
<argument type="service" id="api_platform.router" /> | |||
<argument type="service" id="api_platform.metadata.resource.metadata_factory" /> | |||
<deprecated>The "%service_id%" service is deprecated since API Platform 2.5.</deprecated> |
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.
💡 I haven't found a way to produce an XML file that can be loaded with DependencyInjection 4.4 and 5.1 without errors:
- DI 5.1 triggers a deprecation if the attributes
package
andversion
are missing. - DI 4.4 throws an exception, if those attributes are present.
This is why I'm deprecating the services inside the extension now.
c163d51
to
592dede
Compare
592dede
to
e8749d5
Compare
Thank you very much @derrabus! |
Hi everyone, I still get the error with api-platform/core v2.5.6. Do you know why could it be?
|
Cause this was not yet released: v2.5.6...2.5 |
Oh sorry, i don't know why i thought that because it is merged is released... Thank you @stloyd !! |
Summer and holidays are making things to move at slow pace, bear with us :) |
When do you plan to release it? |
This PR addresses method signatures of the Symfony Config and DependencyInjection components that have changed in Symfony 5.1.