I really don’t get it why this isn’t implemented right.
The values of model.field.label and model.field.help_text are handled to
the modelform so why not also handle model.field.error_messages
--
You received this message because you are subscribed to the Google Groups
"Django developers"
Here is my use case.
Model field definition:
blog_url = models.URLField(verbose_name=u'Blog', blank=True,
error_messages={'invalid': u'Adres bloga nie jest prawidłowy'})
To define error messages in form I have to write:
blog_url = forms.CharField(error_messages={'invalid': u'Adres bloga
Hi Karol,
On 05/02/2012 08:13 AM, Karol Sikora wrote:
According to my ticket: https://code.djangoproject.com/ticket/18237 and
previous one eg.: https://code.djangoproject.com/ticket/13693 I would to
discuss wider this case.
IMHO redefining field in model form subclass to set custom error
message
Hi,
According to my ticket: https://code.djangoproject.com/ticket/18237 and
previous one eg.: https://code.djangoproject.com/ticket/13693 I would to
discuss wider this case.
IMHO redefining field in model form subclass to set custom error messages
is a hardly DRY violation. Currently we have er
