zuhairtaha / note-taking-app Goto Github PK

As I discussed during class, controllers are definitely an optional choice with most express apps. The reason is that in our use case, we had implemented data fetching methods within the class, which correlate very well with methods needed within routes:

https://github.com/zuhairtaha/note-taking-app/blob/master/models/Notes.js

However, in the case where a routes might serve data from more than one model often enough, a controller makes sense, to disentangle class logic with route logic, and let the router only be an overview of offered functionality (more strictly, just a view). For example the MDN docs offer a guide on express which follows this structure, that you were following:

https://developer.mozilla.org/en-US/docs/Learn/Server-side/Express_Nodejs/Displaying_data/Book_list_page