#27039: ModelFields with 'default' value set and 'required'=False in form does
not
use default value
-------------------------------------+-------------------------------------
Reporter: devbis | Owner: nobody
Type: Bug | Status: new
Component: Forms | Version: 1.10
Severity: Release blocker | Resolution:
Keywords: default non- | Triage Stage: Accepted
required modelform |
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
I'd like to hear more about the use case. It might be argued that defaults
should only apply to the population of initial forms and that if a user
removes that value and submits a blank form, Django shouldn't transform it
back to the default. Of course if we decide on that resolution, we'll have
to document the change. If we decide to keep the old behavior, I'm
attaching a regression test.
--
Ticket URL: <https://code.djangoproject.com/ticket/27039#comment:2>
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/064.b701164312eeadb64b9cf1e6417165ce%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
