Contributed by Kévin Dunglas in #40799.
The recommended way of processing Symfony forms is to use a single action for both rendering the form and handling the form submit. This is how it looks in practice: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21// src/Controller/ConferenceController.php // ...
[Route('/{id}/edit', name: 'conference_edit', methods: ['GET', 'POST'])]
public function edit(Request $request, Conference $conference): Response { $form = $this->createForm(ConferenceType::class, $conference);
$form->handleRequest($request);
if ($form->isSubmitted() && $form->isValid()) {
// do something with the $conference object
// (e.g. persist it in the database)
return $this->redirectToRoute('conference_show', [
'id' => $conference->getId(),
]);
}
return $this->render('conference/edit.html.twig', [
'form' => $form->createView(),
]);
}
When using libraries such as Symfony UX Turbo this simple form handling is not enough and you have to follow the HTTP protocol strictly (e.g. if the form is submitted but invalid, the response must have a HTTP 422 status code). In order to simplify the form handling in those cases, Symfony 5.3 adds a new (optional) helper to handle forms. This helper is defined in the AbstractController base controller as a new method called handleForm(). This is how the previous example looks when using the new helper: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25// src/Controller/ConferenceController.php // ...
[Route('/{id}/edit', name: 'conference_edit', methods: ['GET', 'POST'])]
public function edit(Request $request, Conference $conference): Response { return $this->handleForm( $this->createForm(ConferenceType::class, $conference), $request, function (FormInterface $form) use ($conference) { // do something with the $conference object // (e.g. persist it in the database)
return $this->redirectToRoute(
'conference_show',
['id' => $conference->getId()],
Response::HTTP_SEE_OTHER
);
},
function (FormInterface $form) {
return $this->render('conference/edit.html.twig', [
'form' => $form->createView(),
]);
}
);
}
The signature of the handleForm() method is: 1handleForm(FormInterface $form, Request $request, callable $onSuccess, callable $render): Response
Both $onSuccess and $render callables must return a Response object. This is how it works in practice:
if the form is not submitted, the $render callable is called; if the form is submitted but invalid, the $render callable is called and a 422 HTTP status code is set if the current status hasn’t been customized; if the form is submitted and valid, the $onSuccess callable is called (which is usually where you persist the data and return the 303 HTTP redirection).
Sponsor the Symfony project.
http://feedproxy.google.com/~r/symfony/blog/~3/tgna0PcoiTE/new-in-symfony-5-3-form-handler-helper
Connectez-vous pour ajouter un commentaire
Autres messages de ce groupe

The Validator component provides dozens of constraints ready to use in your applications. In Symfony 7.3, we've added two new constraints to the list.
Slug Constraint

SymfonyOnline June 2025 is almost here, starting in almost 2 months on:
June 10-11: Workshop days. It is possible to attend 1 two-day training or 2 one-day trainings. June 12-13: Online confe

Contributed by Jérôme Tamarelle in

This week, we kicked off the New in Symfony 7.3 blog series, highlighting all the exciting new features coming in this release. We also unveiled more details about some of the SymfonyOnline June 2025

SymfonyOnline June 2025 is almost here, starting in almost 2 months on:
June 10-11: Workshop days. It is possible to attend 1 two-day training or 2 one-day trainings. June 12-13: Online confe

Symfony's Messenger component makes it easy to build message-driven applications. However, developers using symfony/amqp-messenger have long faced a limitation: it relies on polling (get()), which can

SymfonyLive Berlin 2025 took place just 3 weeks ago!
A huge thank you to everyone who joined us!🔥 The conference brought together the local Symfony community in the heart of Berlin for two da