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
To record ongoing discussions among tech members for posterity / whoever gets to this next:
It has recently been discussed amoung tech and others that many Dashboard APIs do not actually pertain solely to dashboard. In fact, many of dashboard's APIs / backend code were forked from Tech's/now SIPB's Dormbase projects at some point. Very few, if any, of the subsequent changes have invalidated their original purposes. Most changes would actually be beneficial to Dormbase with minimal changes, should they be transfered back (e.g. the Dining/Menu back end. ).
In addition, API design is non-trivial, and deserves proper attention in its own right.
For these reasons amoung others, it may make sense to abstract these api's into their own project. Dashboard, whatever new Simmons db comes around, and other student projects within Simmons could then use and improve these APIs, especially the related backends, mostly independently.
Obviously, this would greatly change and simplify the flavor of dashboard, and it's not to be taken lightly.
All API apps should be nested under .com/api. Makes intent clearer to developers
The text was updated successfully, but these errors were encountered: