Hi Claude, a few things after a quick glance at it. Overall the feature seems rather simple and I do not see any reason why this would have to be in core from the start; ie it could easily evolve as a 3rd party app.
I am not that much into frontend dev, but from my experience a few things popped up rather quickly: * I generally do not load all js/css in bulk, but rather only the essential stuff in <head> and the rest before the <body> ends. (or even just selecting files by type; css vs js etc…) * The app level seems to be a rather coarse grained separation, I could imagine people wanting more control over it without generating more apps for separation. * How would support for subressource integrity etc look like; integration with the storage system would be interesting here * Any thoughts on asset pipelines? Cheers, Florian On Monday, July 23, 2018 at 5:36:05 PM UTC+2, Claude Paroz wrote: > > Hi, > > I just created a new feature request [1] to be able to define static > files per application, including a POC patch [2]. > > [1] https://code.djangoproject.com/ticket/29586 > [2] https://github.com/django/django/pull/10218 > > Feel free to discuss it here for general discussion on the feature > utility, or comment on the ticket or on the pull request for > implementation details. > > Cheers, > > Claude > -- > www.2xlibre.net > -- 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 post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/25e0a1bd-5592-478b-a06b-ff01b1d5bbe9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
