use handleRequest() instead of bind()

[xabbuh]

Q	A
Doc fix?	yes
New docs?	no
Applies to	2.3+
Fixed tickets	#2969

[xabbuh]

#2965 should be merged before this.

[wouterj]

-1 for the current state. It's the component docs, we should talk about using the form component without the HttpKernel extension awell as with the HttpKernel extension.

[stof]

you should keep the information about the HttpFoundation integration too

[xabbuh]

So, if I understand this correctly, you'd pass the superglobals (i.e. $_REQUEST) to handleRequest(), unless you have registered the HttpFoundationExtension?

[stof]

@xabbuh No, when using the NativeRequestHandler, you call it without argument (or with null as argument)

[xabbuh]

Thanks for the clarification. Think I got it. But, where is the advantage on using the HttpFoundationExtension. For me, calling $form->handleRequest() seems to be simpler than calling $form->handleRequest($request).

[stof]

@xabbuh see the chapter of the doc describing the advantages of HttpFoundation or http://blog.servergrove.com/2013/09/23/symfony2-components-overview-httpfoundation/ for instance.
$form->handleRequest() looks simpler at first, until you start testing your code (it uses super globals, so it relies on a global state and your code will not be testable anymore with the BrowserKit shipped by HttpKernel directly).
If your application uses the HttpFoundation component, you should be using its integration so that your form operates on the same data than the app (it would be confusing if you use a listener to modify the legacy input of your app to the new format and the form does not use the processed input when binding for instance).

[xabbuh]

That makes sense. Should have thought of. Would it be useful to add your explanation to this section?

[weaverryan]

Thanks Christian! I've merged this and added a few more details about what's going on behind the scenes with the handlers (sha: 1beb526). If you see any issues, let me know or make a PR of course :).

Cheers!