From 12806758347dfd63a3cd1bfc0d925c09fdbd9cff Mon Sep 17 00:00:00 2001 From: Tai Lee Date: Tue, 7 May 2013 19:06:03 +1000 Subject: Fixed #15511 -- Allow optional fields on ``MultiValueField` subclasses. The `MultiValueField` class gets a new ``require_all_fields`` argument that defaults to ``True``. If set to ``False``, individual fields can be made optional, and a new ``incomplete`` validation error will be raised if any required fields have empty values. The ``incomplete`` error message can be defined on a `MultiValueField` subclass or on each individual field. Skip duplicate errors. --- docs/releases/1.7.txt | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'docs/releases') diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt index 161ae55436..fbbf93f627 100644 --- a/docs/releases/1.7.txt +++ b/docs/releases/1.7.txt @@ -122,6 +122,11 @@ Minor features ``html_email_template_name`` parameter used to send a multipart HTML email for password resets. +* :class:`~django.forms.MultiValueField` allows optional subfields by setting + the ``require_all_fields`` argument to ``False``. The ``required`` attribute + for each individual field will be respected, and a new ``incomplete`` + validation error will be raised when any required fields are empty. + Backwards incompatible changes in 1.7 ===================================== -- cgit v1.3