runserver_plus autoreload on template change #1796
Conversation
45c14ed to
7bf8b99
Compare
|
I have tested this and can confirm that it reloads updated and new files. |
|
Hi folks, I've just run into this one myself is this likely to be merged any time soon? |
|
Just chiming in to agree that this has solved the issue for me as well (where it was not solved for me in #1775). @trbs any hope of getting a review on this please? 🙏 @foarsitter I suspect it would help if you address the failing pytest checks |
|
Thanks for testing @wgordon17. If I recall correctly, the tests are fixed in #1797 as reported in #1812. |
|
Guess the flip side is that it can be annoying as well that files which has nothing to do with "runserver" triggers a reload... Maybe this kind of behavior would also be nice to be controlled via some cli options && settings.. |
|
Hey guys, anyone else still having this problem? Not working with With django-extensions version 3.2.3 |
|
Open an issue with a minimal failing example if you think the problem still exists. It should be solved in 3.2.3. |
This pull-request is the second attempt (see #1775 for details) to get the correct behavior for reloading of the development server.
The
watchdogreloader did accept the *.html wildcard pattern but thestatreloader isn't.Therefore this pull-request adds an list of all files inside all template directories to
extra_files. Even non .html files inside the template directories are triggering a reload since it can occur other extensions are used for templates like .css & .js. New files added to the template directory also trigger a reload since this is the same behavior asrunserver.Thanks to @bmihelac for providing feedback to my first attempt.