-
-
Notifications
You must be signed in to change notification settings - Fork 848
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
3.1.11 - Validation broken in custom providers #5585
Comments
soyuka
added a commit
to soyuka/core
that referenced
this issue
May 10, 2023
good catch, does my fix work for you ? |
Yes it does, thanks! 👍 |
soyuka
added a commit
that referenced
this issue
May 11, 2023
soyuka
added a commit
to soyuka/core
that referenced
this issue
May 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
API Platform version(s) affected: 3.1.11
Description
#5583 added a very broad catch in
ReadListener
, which will now make all errors happening in providers as 404 ones.How to reproduce
Possible Solution
I'm not sure whether
RuntimeException
should be caught, but a more specific exception class I guessAdditional Context
The text was updated successfully, but these errors were encountered: