Move static files to "table" subdirectory for correct namespacing
shoval opened this issue · 0 comments
The static files for this app are currently under table/static directory, while the best practice is for them to be under table/static/table, as written in the Django documentation:
Now we might be able to get away with putting our static files directly in my_app/static/ (rather than creating another my_app subdirectory), but it would actually be a bad idea. Django will use the first static file it finds whose name matches, and if you had a static file with the same name in a different application, Django would be unable to distinguish between them. We need to be able to point Django at the right one, and the easiest way to ensure this is by namespacing them. That is, by putting those static files inside another directory named for the application itself.