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
At the moment you're setting some of the HTML in templates.js and some of it in your routes (specifically here)
It helps to have a separation of concerns between the routing logic and the templates as an app gets bigger. Say we want to know where a certain css class is set, we should only have to look in one place, ie where the templates live. As the code is at the moment, we would also have to look inside the server routes.
This is a bit difficult to explain in writing so I'll talk about during the live code review tomorrow. Let me know if you have any questions afterwards!
The text was updated successfully, but these errors were encountered:
At the moment you're setting some of the HTML in
templates.js
and some of it in your routes (specifically here)It helps to have a separation of concerns between the routing logic and the templates as an app gets bigger. Say we want to know where a certain css class is set, we should only have to look in one place, ie where the templates live. As the code is at the moment, we would also have to look inside the server routes.
This is a bit difficult to explain in writing so I'll talk about during the live code review tomorrow. Let me know if you have any questions afterwards!
The text was updated successfully, but these errors were encountered: