#4471 closed Uncategorized (wontfix)
Newforms errors.as_text probably shouldn't prefix the string with an '*' character
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Forms | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Design decision needed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
To make
errors.as_text
more generic, it probably shouldn't prefix the returned string with an asterisk. This would give template authors more control over the formatting of error strings.
Attachments (1)
Change History (6)
Changed 16 years ago by
Attachment: | remove_stars_from_errors.diff added |
---|
comment:1 Changed 16 years ago by
Has patch: | set |
---|
comment:2 Changed 16 years ago by
Triage Stage: | Unreviewed → Design decision needed |
---|
comment:3 Changed 15 years ago by
comment:4 Changed 13 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Would be backwards incompatible at this point. Making this change in your own code is easy enough, as it's possible to use a custom Error class on forms and the method can be subclassed.
comment:5 Changed 11 years ago by
Easy pickings: | unset |
---|---|
Severity: | → Normal |
Type: | → Uncategorized |
UI/UX: | unset |
How do I make a custom Error class on my form for 'non_field_errors' so that I can use {{ form.non_field_errors.as_text }}
in my template without the silly '*' throwing off the qì (Ch'i) of my site?
I know it's old, but it still (AFAIK) applies. Let's get rid of the asterisk! I think the diff needs to remove the extra space at the beginning too.