Changes to static files outside the frontend folder requiring make build
Categories
(Webtools Graveyard :: Pontoon, enhancement, P1)
Tracking
(Not tracked)
People
(Reporter: henikilana, Assigned: adrian)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36
Steps to reproduce:
- Edit pontoon/base/static/css/style.css
- Open in browser http://localhost:8000/static/css/style.css
Actual results:
No changes in the browser.
It updates only after running "make build"
Expected results:
The file should be updated.
Comment 1•5 years ago
|
||
Thanks for the report!
:adrian, I'm having this problem as well. Do you mind having a look at this?
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
This is a side-effect of enabling the feature for Translate.Next. I had to use --nostatic
on the runserver
django command, so that I could load static files from the webpack server. But then when I do that, we do lose automatic reloading of django static files.
I'm investigating, but I guess I'll have to find a way to have the effect of the static django utility for resources that are not frontend related. Not sure if or how that's doable.
Comment 3•5 years ago
|
||
Bumping priority, because this makes development on static files outside frontend extremely slow.
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
Updated•3 years ago
|
Description
•