Skip to content

Commit

Permalink
Revert "[#3338] Removing delete_empty details because this is first b…
Browse files Browse the repository at this point in the history
…eing committed to 2.3"

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

This reverts commit 72fa7b4.
  • Loading branch information
weaverryan committed Jan 1, 2014
1 parent 7112444 commit bd1e53e
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions reference/forms/types/collection.rst
Expand Up @@ -19,6 +19,7 @@ forms, which is useful when creating forms that expose one-to-many relationships
| | - `allow_delete`_ |
| | - `prototype`_ |
| | - `prototype_name`_ |
| | - `delete_empty`_ |
+-------------+-----------------------------------------------------------------------------+
| Inherited | - `label`_ |
| | - `label_attr`_ |
Expand Down Expand Up @@ -335,6 +336,16 @@ If you have several collections in your form, or worse, nested collections
you may want to change the placeholder so that unrelated placeholders are not
replaced with the same value.

delete_empty

This comment has been minimized.

Copy link
@wouterj

wouterj Jan 1, 2014

Member

missing versionadded directive

This comment has been minimized.

Copy link
@weaverryan

weaverryan Jan 2, 2014

Author Member

it's added on a later commit :)

~~~~~~~~~~~~

**type**: ``Boolean`` **default**: ``false``

If you want to explicitly remove entirely empty collection entries from your
form you have to set this option to true. However, existing collection entries
will only be deleted if you have the allow_delete_ option enabled. Otherwise
the empty values will be kept.

Inherited options
-----------------

Expand Down

0 comments on commit bd1e53e

Please sign in to comment.