#20267: default form values (not just initial)
-------------------------------+--------------------------------------
Reporter: clime | Owner: nobody
Type: New feature | Status: closed
Component: Forms | Version: 1.5
Severity: Normal | Resolution: worksforme
Keywords: form, default | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by claudep):
Thanks for sharing your use case. You have to admit that it is somewhat
specialized, and do not match the traditional form usage. So I maintain my
original opinion, and with using `clean_order_by`-type methods you can
easily achieve your goals.
I think the role of a framework is to 1. provide easy-to-use tools for the
80% of use cases, 2. provide ways/hooks to customize for the 20% special
needs. And I think the current implementation does a rather good job in
this regard.
But of course, you are free to discuss that and get opinions from others
on django-developers mailing list and point to this ticket for more
details.
--
Ticket URL: <https://code.djangoproject.com/ticket/20267#comment:3>
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 post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
