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
This blog post highlights the key accomplishments of the Symfony project in 2024. We are grateful for your continuous support, which enabled the Symfony project to achieve a remarkable year.
Releases
This week, Symfony 6.4.17, 7.1.10 and 7.2.2 maintenance versions were released. In addition, we published more information about the upcoming SymfonyOnline January 2025 conference.
Symfony developmen
Get ready for the exciting SymfonyOnline January 2025, kicking off shortly on January 16-17! There’s still time to register and join the international online Symfony conference—along with pre-
Symfony 6.4.17 has just been released. Here is the list of the most important changes since 6.4.16:
bug #59304 [PropertyInfo] Remove @internal from PropertyReadInfo and PropertyWriteInfo (Dario G
Symfony 7.1.10 has just been released. Here is the list of the most important changes since 7.1.9:
bug #59304 [PropertyInfo] Remove @internal from PropertyReadInfo and PropertyWriteInfo (Dario Gu
Symfony 7.2.2 has just been released. Here is the list of the most important changes since 7.2.1:
bug #59304 [PropertyInfo] Remove @internal from PropertyReadInfo and PropertyWriteInfo (Dario Gua
This week, we launched the new Twig playground, a tool that lets you test and experiment with Twig features in a safe, sandboxed environment. While Symfony development activity was lighter than usual