Hello, I've got bitten by parts of bug 16226[1] - the default_if_none filter being used and I think it exposes a few issues: - prepopulated_fields is a badly chosen name if it only works for slugs. - the current javascript API allows one to easily complete fields using a declarative syntax - model attributes are arbitrarily exposed to form fields and widgets. For an integer field a max_length attribute is equally valid and probably should be set to the number of base-10 positions of the max_value attribute if max_length is not set.
As aaugustin advises, I'm therefore asking what the devs would like to do with above issues and what the problems are implementing or not implementing the proposed fixes. [1] https://code.djangoproject.com/ticket/16226 -- Melvyn Sopacua -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
