#36913: Optimise ChoiceField / MultipleChoiceField handling of duplicate
submissions
-------------------------------------+-------------------------------------
     Reporter:  Jake Howard          |                    Owner:  Afenomamy
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Forms                |                  Version:  6.0
     Severity:  Normal               |               Resolution:  fixed
     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
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):

 In [changeset:"8b7ea2bcdd7297941ca6beb72d93b9568e187349" 8b7ea2bc]:
 {{{#!CommitTicketReference repository=""
 revision="8b7ea2bcdd7297941ca6beb72d93b9568e187349"
 Refs #36913 -- Maintained error message determinism in
 MultipleChoiceField.validate().

 Used Django's OrderedSet datastructure instead of set() in
 MultipleChoiceField.validate()
 to prevent submission ordering from being discarded during validation.

 Thanks to Jacob Walls, JaeHyuck Sa, Jake Howard and Simon Charette for
 the reviews.
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36913#comment:13>
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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/0107019d2b97d65e-86c1b1a7-13f4-4bc3-b77b-bad7dc2ffda4-000000%40eu-central-1.amazonses.com.

Reply via email to