<p dir="auto">The commit <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/symfony/symfony/commit/7e87eb1fdfac872687a4b9a7ce315812d5eb0d03/hovercard" href="https://github.com/symfony/symfony/commit/7e87eb1fdfac872687a4b9a7ce315812d5eb0d03"><tt>7e87eb1</tt></a> removes the _format param being passed to twig.controller.exception:showAction. No updates were made to the TwigBundle's ExceptionController to account for this change and as such errors or exceptions from non-html requests render incorrectly with the html templates.</p>
<p dir="auto">One possible fix for this is to update the ExceptionController to rely on $request-&gt;getRequestFormat() instead of the $_format argument being passed around in the ExceptionController to its various methods.</p>
<p dir="auto">Hello,</p>
<p dir="auto">I was wondering if it could be interesting to provide a intergration between the security and form components for the login part.<br>
The security listeners for login work with the request object directly. It's easy to create a formType class and use it to display the form, but it will never be submitted.</p>
<p dir="auto">I see two main benefits of using a formType for the login:</p>
<ul dir="auto">
<li>templating: use the same markup as in other form without writing all the html, with the form_* twig functions</li>
<li>validation: ease validation of the scalar values of the fields (without security considerations) like an email format</li>
</ul>
<p dir="auto">Do you think it is worth working on it ? If so where should it live ? Any other recommandations ?</p>
<p dir="auto">Thank you</p>