Commitbd1e53e

committed

Revert "[symfony#3338] Removing delete_empty details because this is first being committed to 2.3"

This re-introduces the delete_empty documentation to the master (2.5) branch, since it should live there.This reverts commit72fa7b4.

1 parent7112444 commitbd1e53eCopy full SHA for bd1e53e

File tree

+11

-0

lines changed

+11

-0

lines changed

Lines changed: 11 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -19,6 +19,7 @@ forms, which is useful when creating forms that expose one-to-many relationships`
`19`	`19`	\|\| - `allow_delete`_\|
`20`	`20`	\|\| - `prototype`_\|
`21`	`21`	\|\| - `prototype_name`_\|
	`22`	+\|\| - `delete_empty`_\|
`22`	`23`	`+-------------+-----------------------------------------------------------------------------+`
`23`	`24`	\| Inherited\| - `label`_\|
`24`	`25`	\|\| - `label_attr`_\|
`@@ -335,6 +336,16 @@ If you have several collections in your form, or worse, nested collections`
`335`	`336`	`you may want to change the placeholder so that unrelated placeholders are not`
`336`	`337`	`replaced with the same value.`
`337`	`338`
	`339`	`+delete_empty`
	`340`	`+~~~~~~~~~~~~`
	`341`	`+`
	`342`	+type: ``Boolean`` default: ``false``
	`343`	`+`
	`344`	`+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 theallow_delete_ option enabled. Otherwise`
	`347`	`+the empty values will be kept.`
	`348`	`+`
`338`	`349`	`Inherited options`
`339`	`350`	`-----------------`
`340`	`351`

Comments

(0)