#24890: Add system check for static files that will always be overwritten on
collectstatic
-------------------------------------+--------------------
Reporter: giuliettamasina | Owner: nobody
Type: New feature | Status: new
Component: contrib.staticfiles | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+--------------------
If you have a project with several apps, some of which have static files
directly in their `static` folder named identically, one of them will
always be overwritten by the other when running `collectstatic`. The
recommendation, and what is noted in the
[https://docs.djangoproject.com/en/1.8/howto/static-files/ documentation],
is to namespace by keeping all static files belonging to an app in an
additional subdirectory in the `static` folder named like the app name.
But if you're not doing that, the result can be very confusing. I've seen
many developers run into this and spending quite some time before figuring
it out through the documentation or otherwise.
I think there should be a default system check that looks for clashing
static file names as described above, and warn if there are files that
will overwrite each other when running `collectstatic`.
--
Ticket URL: <https://code.djangoproject.com/ticket/24890>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/058.c31959e3947cd1fbb0209ceb70735a94%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
