You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, seems like the tables.py, models.py and views.py are just single files containing ALL the table, model and view methods used to render the different pages/tables/views etc... -- Having all the methods in a single file makes it a bit harder to shift through the code and read, in addition to making the files a bit bloated.
Creating this code cleanup issue to organize the files a bit into their respective table/model/view folders/files to make it a bit easier to find the file/method responsible for rendering a particular view.
The text was updated successfully, but these errors were encountered:
Right now, seems like the tables.py, models.py and views.py are just single files containing ALL the table, model and view methods used to render the different pages/tables/views etc... -- Having all the methods in a single file makes it a bit harder to shift through the code and read, in addition to making the files a bit bloated.
Yup, just came across that doc the other day. Not too versed with django package management, was running into some import error when trying to split it up by packages. Will keep looking into this and organizing it as best as I can.
Right now, seems like the
tables.py
,models.py
andviews.py
are just single files containing ALL the table, model and view methods used to render the different pages/tables/views etc... -- Having all the methods in a single file makes it a bit harder to shift through the code and read, in addition to making the files a bit bloated.Creating this code cleanup issue to organize the files a bit into their respective table/model/view folders/files to make it a bit easier to find the file/method responsible for rendering a particular view.
The text was updated successfully, but these errors were encountered: