{"push_id":787117350,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"1a38a9faa980f0f7b5a198530b097cdeb544a9db","before":"65a34cb71d493bb06042ab504018db5b360583bc","commits":[{"sha":"f0c7298510deead6dfbcaa66e8e04493b5c15551","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@acceleration.net","name":"Ryan Davis"},"message":"add firebase support\n\nsorry, another huge commit.\n\n* add another storage backend that uses firebase.com; what firebase\n  application is based on a user setting that is still kept in\n  localstorage\n* tested and rejected the firebase angular lib, built a small wrapper\n  around their JS object using `$q` that doesn't need a bunch of manual\n  `$scope.$apply()` crap\n* use `uuid` to generate ids for firebase; their `push` method is a\n  little cumbersome compared to `uuid.v4()`\n* add a \"remove\" option for chore activity\n* connect to firebase on startup if we're configured to do so\n\nI'm not happy with the factory method in `chores.js` to figure out which\nbackend to use, I'd like to get that into DI, but I'm not sure if that's\nbetter as a routing `resolve` entry or add it to settings. I think I can\nalso reduce the difference between firebase and localstorage persistence\nby using a common data format.","distinct":true,"url":"https://api.github.com/repos/ryepup/chore-cat/commits/f0c7298510deead6dfbcaa66e8e04493b5c15551"},{"sha":"1a38a9faa980f0f7b5a198530b097cdeb544a9db","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@acceleration.net","name":"Ryan Davis"},"message":"create a bundle for deployment with browserify","distinct":true,"url":"https://api.github.com/repos/ryepup/chore-cat/commits/1a38a9faa980f0f7b5a198530b097cdeb544a9db"}]}