Permalink
Browse files

minor #4703 Fix representation (ifdattic)

This PR was merged into the 2.3 branch.

Discussion
----------

Fix representation

It might be just me, but with `unless` it sounds like **if you want to use your forms in multiple places you should define it in your controllers**.

| Q             | A
| ------------- | ---
| Doc fix?      | yes
| New docs?     | no
| Applies to    | 2.3
| Fixed tickets |

Commits
-------

6a55617 Update forms.rst
3d62349 Fix representation
  • Loading branch information...
weaverryan committed Jan 3, 2015
2 parents aa9d982 + 6a55617 commit 1d5966c422f190a7b227ca49d146d6d8af03ad7b
Showing with 2 additions and 2 deletions.
  1. +2 −2 best_practices/forms.rst
@@ -13,8 +13,8 @@ Building Forms
Define your forms as PHP classes.
The Form component allows you to build forms right inside your controller
code. Honestly, unless you need to reuse the form somewhere else, that's
totally fine. But for organization and reuse, we recommend that you define each
code. This is perfectly fine if you don't need to reuse the form somewhere else.
But for organization and reuse, we recommend that you define each
form in its own PHP class::
namespace AppBundle\Form;

0 comments on commit 1d5966c

Please sign in to comment.