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, we've got three separate pages being maintained in the front-end. If we wanted, we could collapse those down to a single main.js instead of having separate tree-view, query and search sub-folders.
PRO: No more messing with the project.clj file when we put in a new javascript page section. CON: Heavier javascript load on each JS-enabled page, which will grow with each piece of functionality we put together.
Not sure how bad the CON really is, because I get the sneaking suspicion that we might be headed towards a single-page-app model at some point in the future, but I have no idea how soon that might be or if we're actively thinking about it.
The text was updated successfully, but these errors were encountered:
Right now, we've got three separate pages being maintained in the front-end. If we wanted, we could collapse those down to a single
main.js
instead of having separatetree-view
,query
andsearch
sub-folders.PRO:
No more messing with theproject.clj
file when we put in a new javascript page section.CON:
Heavier javascript load on each JS-enabled page, which will grow with each piece of functionality we put together.Not sure how bad the CON really is, because I get the sneaking suspicion that we might be headed towards a single-page-app model at some point in the future, but I have no idea how soon that might be or if we're actively thinking about it.
The text was updated successfully, but these errors were encountered: