-
Notifications
You must be signed in to change notification settings - Fork 708
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
Symfony 4.4 compatibility: use Either ErrorListener or ExceptionListener #2031
Comments
Should be fixed by #2025 |
That PR does not resolve the issue. please reopen. |
Can you provide some more information on what happens? |
This is converting the Exception to a FlattenedException, because the parameter here has no type. Which results in a type error here: Adding a type to $exception would fix it. But like i said in OP, This bundle is uses the deprecated ExceptionListener In symfony 4.4 this class is deprecated in favor of ErrorListener. This bundle needs to detect if the consumer is using either |
related: since this bundle now supports symfony 5, this is totally broken since the class doesn't exist. |
Yes, I can confirm that #2025 does not work in 5.0 and triggers another deprecation on 4.4. The ExceptionListener was deprecated while PR was alive. I will try to rework it this weekend. |
See #2036 |
how to fix this problem in Symfony 4.4? |
#2036 already fix this problem on 4.4, but it's not merged yet. |
when going to merge it? because I have the same error |
are there a work around for this? meanwhile |
@emimarz this hack seems to solve it for me and a few others on Symfony 4.4 |
This bundle currently has integration with with the symfony
ExceptionListener
here:https://github.com/FriendsOfSymfony/FOSRestBundle/blob/7705fa0af878f28d56a182dea4f18c1e0ab9cbbb/EventListener/ExceptionListener.php
In symfony 4.4 this class is deprecated in favor of ErrorListener.
A Compiler Pass is used to use either one or the other.
This bundle needs support for both eventualities/listeners.
The text was updated successfully, but these errors were encountered: