#26844: Formset's validate_min doesn't work correctly with empty forms
----------------------------+---------------------------------------------
Reporter: Wim Feijen | Owner: Manasa Patibandla
Type: Bug | Status: new
Component: Forms | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+---------------------------------------------
Changes (by Jim Ouwerkerk):
* status: closed => new
* resolution: fixed =>
Comment:
Replying to [comment:5 Tim Graham <timograham@…>]:
> In [changeset:"f5c6295797b8332134fd89e0209a18a1d1d45e0c" f5c6295]:
> {{{
> #!CommitTicketReference repository=""
revision="f5c6295797b8332134fd89e0209a18a1d1d45e0c"
> Fixed #26844 -- Made formset's validate_min validation ignore empty
forms.
> }}}
This commit breaks the validate_min validation for formset with existing
unchanged data in Django 1.11.
It counts unchanged existing forms as 'empty' form because they are not
changed, but they should not be counted as empty.
--
Ticket URL: <https://code.djangoproject.com/ticket/26844#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.b0b7de58150428a8effc33f9bbcef591%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
