I'm in favor of the change. It seems to me that most slugs I see these days have stop words in them and they read better because of that. I don't think JavaScript warnings would be helpful. A release note is sufficient. Admin users still get a preview of the slug and can edit it if needed.
On Friday, May 15, 2020 at 6:44:12 PM UTC-4, Scott Cranfill wrote: > > Does anyone else have an opinion on whether or not we should still be > removing these stopwords? > > Hopefully someone more involved in i18n can weigh in. >> > > I'm not sure if there are any i18n concerns here. In fact, ceasing this > practice removes the impetus for the recurring issues being raised about > how this practice negatively affects the experience for users of other > languages, or doesn't remove words in their language, etc. > > Thanks for the suggested code, Adam. On the topic of deprecation, in > general: Andy I weren't really sure how to approach that for a > JavaScript-only change. We can't throw deprecation warnings in the Django > console like we could if we were talking about Python code, can we? I could > see adding some more aggressive messaging, maybe even in the Admin? > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/bd4e8c7d-4f7e-4c00-9e8b-49378eb261ee%40googlegroups.com.
