-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Update NotNormalizableValueException with the attribute information #42733
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
Hey! I see that this is your first PR. That is great! Welcome! Symfony has a contribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
see #42502 |
/cc @lyrixx |
This PR needs a rebase to see what's going on IMHO. Because ATM, there is too much difference between what lives in 5.4 and this PR |
OK, I had a better look at this PR and I think it can be closed because I implemented it in #42502 Basically, you can use There is a full example in the test: symfony/src/Symfony/Component/Serializer/Tests/SerializerTest.php Lines 743 to 1053 in 726d360
|
Thank you for the review. |
It's currently not possible to get the information about which attribute is raising the exception (except by doing regex in the exception message string). Having this information allows to handle the error effectively upstream.
It's similar to #42712 but for a different exception.