+1 cleanfield_foo() On 5/14/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > On Mon, 2007-05-14 at 09:11 -0500, Adrian Holovaty wrote: > > Hi there, > > > > I just spotted changeset [5231]: > > > > """ > > Renamed form-specific cleaning methods to be do_clean_*, rather than > clean_*. > > This avoids a name clash that would occur when you had a form field > called > > "data" (because clean_data is already a dictionary on the Form class). > > """ > > http://code.djangoproject.com/changeset/5231 > > > > Well spotted, Malcolm! But I think do_clean_*() is awkward sounding. > > Could we think of a better naming convention, ideally one that uses a > > single word rather than two ("do clean")? > > > > Some suggestions to get the discussion started: > > > > cleanfield_foo() > > validate_foo() > > Sure, I'm not particularly attached to the name, either. It's entirely > undocumented at the moment, so feel free to make up a better name. > > I think we should try to stay with the "cleaning" line of thinking, > rather than validate- or normalise-related terms, just for consistency, > though. > > Malcolm > > > > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
