{"push_id":595444899,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"b645ffebc0a2d6df94d6a38c73827b349d18cbaa","before":"550ac303cc1d5a7dbda1295a5764655899120f95","commits":[{"sha":"9d98ba63bd4a566b42d6a9e1cfaa0528c760b2c1","author":{"email":"1dc92ef42dd4a9b5cf1cf135ebbd3434b0189447@gmail.com","name":"Sam Saccone"},"message":"Update Marionette 2.4.1","distinct":true,"url":"https://api.github.com/repos/tastejs/todomvc/commits/9d98ba63bd4a566b42d6a9e1cfaa0528c760b2c1"},{"sha":"4ae8c9f68a76bbaab34d8fdaf981af73ff43ab4a","author":{"email":"1dc92ef42dd4a9b5cf1cf135ebbd3434b0189447@gmail.com","name":"Sam Saccone"},"message":"Remove use of deprecated AppRegions.\n\nMarionette has marked `appRegions` as a deprecated feature because it is a\nleaky abstraction for the Application to know so much about the DOM and\nthe structure of your actual page.\nInstead of using `appRegions`, Marionette encourages you to setup a\nRootLayout whose concern is setting up render targets.\n\nIn the near future we are introducing the concept of a \"root\" to the\napplication object\nhttps://github.com/marionettejs/backbone.marionette/issues/2279\n\nSo that uses will have an idiomatic way of using this pattern. The goal\nhere is not to conflate the concerns of splitting up render targets\nwith your application, rather the goal is to give users a pattern to follow when\nsetting up a single or multiple application objects.\n\nFixes #1171\nFixes #1184","distinct":true,"url":"https://api.github.com/repos/tastejs/todomvc/commits/4ae8c9f68a76bbaab34d8fdaf981af73ff43ab4a"},{"sha":"b645ffebc0a2d6df94d6a38c73827b349d18cbaa","author":{"email":"8d94591d6660fba452c82da40792f0ec190fa31c@gmail.com","name":"Addy Osmani"},"message":"Merge pull request #1185 from samccone/sjs/remove-application-regions\n\nUpdate Marionette & Remove Deprecated Feature use","distinct":true,"url":"https://api.github.com/repos/tastejs/todomvc/commits/b645ffebc0a2d6df94d6a38c73827b349d18cbaa"}]}