#5374: We need a validator for ModelAdmin classes
-------------------------------------+--------------------------------------
Reporter: jkocherhans | Owner: mrts
Status: new | Milestone: 1.0 alpha
Component: Core framework | Version: newforms-admin
Resolution: | Keywords: nfa-blocker
Stage: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 1
Needs_better_patch: 1 |
-------------------------------------+--------------------------------------
Comment (by mrts):
Note the following:
{{{
<jkocherhans> mrts: we're probably not going to be able to design a nice
system for validation before 1.0, so a function that does the validation
is
probably fine... no need to over-engieer anything or provide hook for
custom
classes to allow their own validation.
<mrts> it doesn't hurt though...
<jkocherhans> I'd argue that it *does* hurt though, cause then we're
committing to an api even if it isn't documented, people will use it
<mrts> should I remove the calls to _call_validation_hook(cls, model)
then?
<jkocherhans> mrts: I'd say yes, but you should probably get a second
opinion
<jkocherhans> mrts: I'm not arguing that they're not useful, I'm arguing
that
it's a design decision, and I know that malcolm and some other people have
opinions about what should happen
}}}
--
Ticket URL: <http://code.djangoproject.com/ticket/5374#comment:11>
Django Code <http://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 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
-~----------~----~----~----~------~----~------~--~---
