Traditionally in MVC architecture, models are designed to be robust and controllers are kept minimal for easier testing. However, Angular lacks a clear model structure, making it challenging to organize code for reuse.
Although Angular does offer services where API queries can be stored, controllers often end up bulky due to numerous callbacks. I've realized that by utilizing routeProviders to resolve data, I can potentially lessen the complexity within my controllers. But is this considered a best practice? Resolve functions always execute before controllers, so when should promises be handled in the controller versus the resolve?