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
[Form] TransformationFailedException is swallowed #9989
Comments
This is correct. The |
OK I see I missed that ... |
Looking at the code there is another issue with this approach - code taken from the cookbok. If I would need to report any details from the failing transformation as in this example the only thing I can determine is that if failed which is
|
In the event that transformation fails, the form is designed to fail gracefully and display the non transformed version of the data in the output. cc / @bschussek |
In my use case the transformation is relevant and it's vital that it succeeds.
I have a service resolver that translates the URL into a subrequest in symfony and returns the UUID of the resource if it's valid otherwise it should fail and I should be able to send a message to the client that the entered country is not valid. the command object and the end of the form expects uuids not URLs. maybe a sort of |
Transformation errors will result in a general "Invalid value" error message. |
IMO, it is related to #9891 |
Here is another use case that comes to my mind - let's start again with the transfomer example that is supposed to return an issue. We can have a form for example that creates a new work log that as an issue field.
then in the form this will fail because issue is not initialized and this happens before you have a chance to
|
The thrown TransformationFailedException is swallowed by the form component
it is happening in the code block bellow
excerpt from Form.php starting at line 631
The text was updated successfully, but these errors were encountered: