8000 [#3338] Removing delete_empty details because this is first being com… · symfony/symfony-docs@72fa7b4 · GitHub
[go: up one dir, main page]

Skip to content

Commit 72fa7b4

Browse files
committed
[#3338] Removing delete_empty details because this is first being committed to 2.3
Since the original PR had a mix of changes that should apply to 2.3+ and 2.5+, I've merged the entire PR into 2.3 and this commit removes the 2.5+ specific documentation. After merging into master (i.e. 2.5), I'll reverse this commit to put the delete_empty details back.
1 parent 0d387af commit 72fa7b4

File tree

1 file changed

+0
-11
lines changed

1 file changed

+0
-11
lines changed

reference/forms/types/collection.rst

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,6 @@ forms, which is useful when creating forms that expose one-to-many relationships
1919
| | - `allow_delete`_ |
2020
| | - `prototype`_ |
2121
| | - `prototype_name`_ |
22-
| | - `delete_empty`_ |
2322
+-------------+-----------------------------------------------------------------------------+
2423
| Inherited | - `label`_ |
2524
| | - `label_attr`_ |
@@ -336,16 +335,6 @@ If you have several collections in your form, or worse, nested collections
336335
you may want to change the placeholder so that unrelated placeholders are not
337336
replaced with the same value.
338337

339-
delete_empty
340-
~~~~~~~~~~~~
341-
342-
**type**: ``Boolean`` **default**: ``false``
343-
344< 6A8E code>-
If you want to explicitly remove entirely empty collection entries from your
345-
form you have to set this option to true. However, existing collection entries
346-
will only be deleted if you have the allow_delete_ option enabled. Otherwise
347-
the empty values will be kept.
348-
349338
Inherited options
350339
-----------------
351340

0 commit comments

Comments
 (0)
0