8000 Remove absolutes url · adam187/symfony-docs@cf32b4c · GitHub
[go: up one dir, main page]

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit cf32b4c

Browse files
committed
Remove absolutes url
1 parent ae877f2 commit cf32b4c

File tree

1 file changed

+6
-9
lines changed

1 file changed

+6
-9
lines changed

best_practices/forms.rst

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -69,9 +69,11 @@ To use the class, use ``createForm`` and instantiate the new class:
6969
Registering Forms as Services
7070
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7171

72-
You can also `register your form type as a service`_. But this is *not* recommended
73-
unless you plan to reuse the new form type in many places or embed it in
74-
other forms directly or via the `collection type`_.
72+
You can also
73+
:ref:`register your form type as a service <form-cookbook-form-field-service>`.
74+
But this is *not* recommended unless you plan to reuse the new form type in many
75+
places or embed it in other forms directly or via the
76+
:doc:`collection type </reference/forms/types/collection>`.
7577

7678
For most forms that are used only to edit or create something, registering
7779
the form as a service is over-kill, and makes it more difficult to figure
@@ -169,7 +171,7 @@ fields:
169171

170172
If you need more control over how your fields are rendered, then you should
171173
remove the ``form_widget(form)`` function and render your fields individually.
172-
See `How to Customize Form Rendering`_ for more information on this and how
174+
See :doc:`/cookbook/form/form_customization` for more information on this and how
173175
you can control *how* the form renders at a global level using form theming.
174176

175177
Handling Form Submits
@@ -210,8 +212,3 @@ Second, we recommend using ``$form->isSubmitted()`` in the ``if`` statement
210212
for clarity. This isn't technically needed, since ``isValid()`` first calls
211213
``isSubmitted()``. But without this, the flow doesn't read well as it *looks*
212214
like the form is *always* processed (even on the GET request).
213-
214-
.. _`register your form type as a service`: http://symfony.com/doc/current/cookbook/form/create_custom_field_type.html#creating-your-field-type-as-a-service
215-
.. _`collection type`: http://symfony.com/doc/current/reference/forms/types/collection.html
216-
.. _`How to Customize Form Rendering`: http://symfony.com/doc/current/cookbook/form/form_customization.html
217-
.. _`form event system`: http://symfony.com/doc/current/cookbook/form/dynamic_form_modification.html

0 commit comments

Comments
 (0)
0