This PR is preparing me to take the workshop and transform it to the blocks configuration.
Using the Angular router (like in many SPA frameworks), the router is actually responsible for fetching the data, not the controller. So I moved the behavior of model fetching to the route, and I pass it to the component as a "model" parameter, which the component can give a better name to.
I also took this opportunity to clean up the model code a bit. We don't need to include $q in the model functions because the angular-pouchdb module does it for us. We can just chain the promises.
This PR is preparing me to take the workshop and transform it to the blocks configuration.
Using the Angular router (like in many SPA frameworks), the router is actually responsible for fetching the data, not the controller. So I moved the behavior of model fetching to the route, and I pass it to the component as a "model" parameter, which the component can give a better name to.
I also took this opportunity to clean up the model code a bit. We don't need to include
$qin the model functions because theangular-pouchdbmodule does it for us. We can just chain the promises.