#15307: slugify should take an optional max length
-------------------------------------+-------------------------------------
Reporter: jdunck | Owner: nobody
Type: New feature | Status: closed
Component: Template system | Version: 1.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Design
Has patch: 0 | decision needed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* ui_ux: => 0
* resolution: => wontfix
* easy: => 0
Comment:
Indeed, I'm not sure this belongs to core:
- The relation to the `max_length` of `SlugField` isn't obvious to me —
and if a form field was involved, a human would be better than a computer
at shortening its contents while preserving its meaning.
- It's easy to implement your idea as a custom template filter (I hope
you've done so).
- I'd prefer to keep slugify simple.
Thanks for the suggestion anyway!
--
Ticket URL: <https://code.djangoproject.com/ticket/15307#comment:4>
Django <https://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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
