#31511: Allow stopwords in slugs generated by ModelAdmin.prepopulated_fields
-------------------------------------+-------------------------------------
Reporter: Andy Chosak | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: contrib.admin | Version: master
Severity: Normal | Resolution: duplicate
Keywords: urlify, slugify, | Triage Stage:
slug | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Comment (by Scott Cranfill):
Hi Mariusz,
Thanks for your feedback. Andy and I weren't sure how long to wait for
more feedback on the mailing list discussion we opened, so we thought
starting the ticket and offering a patch might move things along. Happy to
take the discussion back there, but I will respond to your comment here,
since you haven't commented there yet.
We respectfully disagree that this is a duplicate of #11157. That ticket
was more general, addressing the question of whether `slugify` and
`URLify` should behave the same. The issue we are raising is about
changing a specific behavior that exists only in `URLify`, independent of
anything to do with `slugify`.
Looking forward to further discussion!
--
Ticket URL: <https://code.djangoproject.com/ticket/31511#comment:3>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.ba280068f3508f109a542f971424c196%40djangoproject.com.
