#3193: [patch] modify as_hidden() to handle MultipleChoiceField correctly
-----------------------------------------------+----------------------------
Reporter: Honza Kr�l <[EMAIL PROTECTED]> | Owner: adrian
Type: defect | Status: new
Priority: normal | Milestone:
Component: django.newforms | Version: SVN
Severity: normal | Resolution:
Keywords: as_hidden MultipleChoiceField |
-----------------------------------------------+----------------------------
Comment (by Honza Kr�l <[EMAIL PROTECTED]>):
I originally thought of using the requires_list field, but it was no
longer there so I decided not to add another field with roughly the same
meaning...
btw. it seems more natural to me for {{{as_hidden}}}, {{{as_text}}} etc to
be handled by {{{Field}}} and not {{{BoundField}}} - the latter knows
nothing about the data (as demonstrated in this problem) and therefore
cannot adapt its behaviour, the {{{Field}}} seems better suited for this.
--
Ticket URL: <http://code.djangoproject.com/ticket/3193#comment:>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django
updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
