{"push_id":638921101,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"a45bd8c23984dbd956943070651ea224a7b6e4af","before":"5d8221efaf821060dd205c8dc7acd4157e40b48c","commits":[{"sha":"9c80ac907c4244b146df06273518ba8b0727a3c7","author":{"email":"a027184a55211cd23e3f3094f1fdc728df5e0500@planar.id.au","name":"Paul Lambert"},"message":"doc(tut): add example code to grouping","distinct":true,"url":"https://api.github.com/repos/angular-ui/ng-grid/commits/9c80ac907c4244b146df06273518ba8b0727a3c7"},{"sha":"10dc29be2296693caabe1de0446b78f25261d3e3","author":{"email":"a027184a55211cd23e3f3094f1fdc728df5e0500@planar.id.au","name":"Paul Lambert"},"message":"Fix(scrolling): dreadful iPad performance, badly formed\n\nA handful of issues, mostly comes down to poor use of $interval in the throttle method (my\nchange), and also fixing a defect where the aggregations weren't calculated by turning the\nthrottle into a trailing throttle.  This resulted in the grid waiting 0.5s before running the\naggregation, but the aggregation triggered a $digest since a bound value had changed, and in turn\nthat called aggregation again.\n\nMoved the aggregation call to be triggered by the rowsRendered event.  This event is emitted\nwhenever visible rows change, which should suit aggregation.  This meant I had to move the\ncall to aggregation into the gridFooterCell, as I needed a destroy event in order to destroy the\nregistered api listener.","distinct":true,"url":"https://api.github.com/repos/angular-ui/ng-grid/commits/10dc29be2296693caabe1de0446b78f25261d3e3"},{"sha":"a45bd8c23984dbd956943070651ea224a7b6e4af","author":{"email":"9d4cb9bd1d9ee56d1c22858d7fa4b901423530f0@users.noreply.github.com","name":"Paul"},"message":"Merge pull request #3322 from PaulL1/fixes2\n\niPad performance - spare watchers and aggregations","distinct":true,"url":"https://api.github.com/repos/angular-ui/ng-grid/commits/a45bd8c23984dbd956943070651ea224a7b6e4af"}]}