ux: [LiveComponent] Custom form errors not displayed when invoking live action
Hi there.
I believe I encountered an issue with the Symfony UX’s ComponentWithFormTrait where form errors are not displayed when a live action is invoked from a component template.
To give a brief context: I have some business logic that throws some very specific Domain Errors that I would need to map and display to the user.
I’m using the ComponentWithFormTrait to handle forms in my live component.
When invoking a live action, I’m trying to add both global form errors and specific field errors. However, despite adding these errors, they are not displayed in the form.
Reproduction Steps:
- Create a form using
ComponentWithFormTrait. - In the live action method, add a global form error and a field-specific error.
- Invoke the live action from the component template.
- Observe that the errors are not displayed in the form.
Minimal Reproducible Code: Component:
use ComponentWithFormTrait;
#[LiveAction]
public function save()
{
// Attempting to add a global form error
$this->getForm()->addError(new \Symfony\Component\Form\FormError('General error'));
// Attempting to add a specific field error
$this->getForm()->get('description')->addError(new \Symfony\Component\Form\FormError('Form field error'));
}
Template:
<div {{ attributes }}>
{{ form_start(form, {
attr: {
'data-action': 'live#action',
'data-action-name': 'prevent|save'
}
}) }}
{{ form_errors(form) }}
{{ form_row(form.description) }}
<button type="submit">Save</button>
{{ form_end(form) }}
</div>
If it makes any difference, my form is using a data-transfer object for the form data. I have noticed that with a regular Symfony action+Twig template this does work.
I suspect that somehow the form instance might not be the same getting rendered?
Is this a known issue, or is there a recommended way to force the form errors to display in this scenario?
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 1
- Comments: 15 (3 by maintainers)
Yes, I’m throwing an
UnprocessableEntityExcetion. I believe I have found the problem and a workaround for it.When calling some live action method, the first call is to
submitFormOnRender, and if the form was not yet submitted form then it’s submitted, it gets validated, and then theformViewis filled. Later when a custom exception is thrown, we associate the error to the form, and throw anUnprocessableEntityExcetionso then it’s handled by the methodonKernelExceptionof the classLiveComponentSubscriber. There it will try to create a response using theComponentRenderer, that will try to obtain the component variables and then render the associated twig template with those variables. The methodexposedVariablesis obtaining the exposedformView(#[ExposeInTemplate(name: 'form', getter: 'getFormView')]), the problem is that thisformViewis cached, so it only contains the initial status, and not the new error that was added later.A workaround that worked for me was to reset the
formViewto force it to be calculated again.Taking the example from @IvoPereira
Thanks for the quick reply.
Let me provide a bit more context (I didn’t provide it initially, as I believed the issue was not related).
In my forms, after
submitForm()and being sure the form is valid, I usually dispatch a handler/call a service to validate/persist my domain data.Let’s say I am building a signup form. I have in my service a validation that checks for instance whether the given email is unique. If it isn’t, it throws an
EmailAlreadyInUseException.Tldr; while the majority of invalid fields can be caught using the form validations, I need to catch service
Exceptionsand map them to form fields asFormErrorsas well.Simplified example: