Skip to content

Commit f4492c9

Browse files
committed
Merge branch '4.4' into 5.4
* 4.4: Fix typos of the Dynamic Form Modification document remove form types from TOC that have been introduced in later versions
2 parents 7820ef8 + 1fce371 commit f4492c9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

form/dynamic_form_modification.rst

+3-3
Original file line numberDiff line numberDiff line change
@@ -230,7 +230,7 @@ Using an event listener, your form might look like this::
230230
}
231231

232232
The problem is now to get the current user and create a choice field that
233-
contains only this user's friends. This can be done injecting the ``Security``
233+
contains only this user's friends. This can be done by injecting the ``Security``
234234
service into the form type so you can get the current user object::
235235

236236
use Symfony\Component\Security\Core\Security;
@@ -490,7 +490,7 @@ The type would now look like::
490490
$sport = $event->getForm()->getData();
491491

492492
// since we've added the listener to the child, we'll have to pass on
493-
// the parent to the callback functions!
493+
// the parent to the callback function!
494494
$formModifier($event->getForm()->getParent(), $sport);
495495
}
496496
);
@@ -510,7 +510,7 @@ exactly the same things on a given form.
510510
the listener is bound to, but it allows modifications to its parent.
511511

512512
One piece that is still missing is the client-side updating of your form after
513-
the sport is selected. This should be handled by making an AJAX call back to
513+
the sport is selected. This should be handled by making an AJAX callback to
514514
your application. Assume that you have a sport meetup creation controller::
515515

516516
// src/Controller/MeetupController.php

0 commit comments

Comments
 (0)