{"push_id":710493014,"size":35,"distinct_size":35,"ref":"refs/heads/only-invoke-still-present-chain-entries","head":"20b16a5bf0f991aaa22db49a72de31fa63fc91d6","before":"77c6dfeffe460dfcc80b134cc8452c5f23133668","commits":[{"sha":"7847cc48290f00344c73dd87029613bbd6985b7e","author":{"email":"0b40b374491a9d33ce3192c35cb80116802ee83a@gmail.com","name":"Stefan Penner"},"message":"Revert \"Fixes: Safari's 'double finally on error bug'\"\n\nThis reverts commit 917da11e1814d88106b5c62022486c716a94afaf.\n\niOS 6 makes up less the 4% of the iOS market, and this bug appears to be\nfixed in iOS 6.1. As such the potentially affected devices is quite\nsmall. Finally, the bug only comes into play in very specific failure\nscenarios which are nearly all already handled in backburner.","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/7847cc48290f00344c73dd87029613bbd6985b7e"},{"sha":"ea004a5105a0864958d26308807021c94ae807a3","author":{"email":"6f0d3293b01c3c713bd55d77d142f634b67e11e3@me.com","name":"James Murphy"},"message":"[BUGFIX release] Sticky query params for nested and for dynamic routes.\n\nFixed query params not being sticky for nested routes\n\nFixed query params not working for multiple routes that each have a dynamic segment\nPrevious only 1 dynamic segment was working correctly","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/ea004a5105a0864958d26308807021c94ae807a3"},{"sha":"0dc1a6c73258d891fe54014754c33772310d7b48","author":{"email":"0b40b374491a9d33ce3192c35cb80116802ee83a@gmail.com","name":"Stefan Penner"},"message":"[BUGFIX beta] [fixes #11181, #10343, #9739, #9462, #4919, #4231, #3706, #5596, #9485, #9492, #5319, #5268, #4831, #5558] Move away from AC/RC instead use the simpler naive enumerable methods, and rely on glimmers stable rendering for efficiency.\n\nFor more complex scenarios, custom solutions should be used.\n\n@wagenet & @stefanpenner","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/0dc1a6c73258d891fe54014754c33772310d7b48"},{"sha":"9c52115bf3a2f20bf560dfe8b7b5d26aa1e8372c","author":{"email":"0b40b374491a9d33ce3192c35cb80116802ee83a@gmail.com","name":"Stefan Penner"},"message":"only invoke didChange if a node is still present.","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/9c52115bf3a2f20bf560dfe8b7b5d26aa1e8372c"},{"sha":"e189688d40c738ce3ccbdde39f336d50e6909432","author":{"email":"0053807ec1f2a1bdf2f78124556471d1cfa44341@gmail.com","name":"Julien Guimont"},"message":"Rerender link on routing state change.\nTest link-to with only query params provided","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/e189688d40c738ce3ccbdde39f336d50e6909432"},{"sha":"9c919caee8c63f37504bcf21f06ecb4ccba9e536","author":{"email":"b1c1d8736f20db3fb6c1c66bb1455ed43909f0d8@rwjblue.com","name":"Robert Jackson"},"message":"Merge pull request #11547 from stefanpenner/revert-ios-6.0.x-double-finally-on-error\n\nRevert \"Fixes: Safari's 'double finally on error bug'\"","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/9c919caee8c63f37504bcf21f06ecb4ccba9e536"},{"sha":"47ec66225a6c2a01aca8d38a2b4fa2a334da32b6","author":{"email":"b1c1d8736f20db3fb6c1c66bb1455ed43909f0d8@rwjblue.com","name":"Robert Jackson"},"message":"Merge pull request #11513 from stefanpenner/remove-rc-dc\n\nMove away from ArrayComputed/ReduceComputed","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/47ec66225a6c2a01aca8d38a2b4fa2a334da32b6"},{"sha":"dc479cef91c1b9815157612c2a2f9483a2a04edc","author":{"email":"b1c1d8736f20db3fb6c1c66bb1455ed43909f0d8@rwjblue.com","name":"Robert Jackson"},"message":"Merge pull request #11561 from juggy/query-params-links\n\n[BUGFIX release] Rerender link on routing state change.","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/dc479cef91c1b9815157612c2a2f9483a2a04edc"},{"sha":"248335def4d8b9f2df062543a8234d92809f7699","author":{"email":"16a9a54ddf4259952e3c118c763138e83693d7fd@responsis.com.au","name":"Joe Ruello"},"message":"[DOC release] Mark transitionTo as public","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/248335def4d8b9f2df062543a8234d92809f7699"},{"sha":"2579522a9e137af2e9fceda4aee5855042e9328d","author":{"email":"96835dd8bfa718bd6447ccc87af89ae1675daeca@tomdale.net","name":"Tom Dale"},"message":"[BUGFIX release] Don’t force invalidation of block param streams\n\nThis commit removes the forced invalidation of block param streams on\nre-renders.\n\nPreviously, on re-renders, all block param streams were revalidated by\ncalling `notify()` on them blindly.\n\nWhile this often works, it creates a vector for light scopes to\ninadvertently invalidate their associated shadow scopes. In some cases,\nthis leads to an infinite loop.\n\nFor example, imagine a component with the following template:\n\n```handlebars\n{{! app/templates/components/block-with-yield.hbs }}\n{{yield danger}}\n```\n\n(Here `danger` is a property on the component.)\n\nNow we invoke it:\n\n```handlebars\n{{#block-with-yield as |dangerBlockParam|}}\n  {{dangerBlockParam}}\n{{/block-with-yield}}\n```\n\nThis works. The yielded block (light scope) receives a stream for the\n`danger` value. On re-renders, the stream is invalidated, but all that\nhappens is the `{{dangerBlockParam}}` render node is dirtied again\n(which doesn’t matter, because we haven’t rendered and cleaned it yet).\n\nHowever, imagine we change the component template to now display the\nsame `{{danger}}` value:\n\n```handlebars\n{{! app/templates/components/block-with-yield.hbs }}\n{{danger}}\n{{yield danger}}\n```\n\nNow, when the block param stream is invalidated, it goes back and\ndirties the render node _from the parent shadow scope_. Because the\ncomponent is dirtied, its `{{yield}}` helper is dirtied, causing the\nblock param streams to be dirtied, and so on in an infinite loop.\n\nThis commit removes the forced invalidation, which I believe is\nunnecessary and probably left over from an earlier implementation.\nSpecifically, if we are yielded a stream (`{{yield danger}}`), the\nstream should notify us of any changes to the value. Any downstream\nconsumers of that stream will be notified correctly.\n\nIn the case of `{{yield “hello”}}` or some other primitive, we already\nwrap those values in a `ProxyStream` and call `setSource` when it\nchanges, which has the effect of invalidating the stream anyway.\n\nCloses #11519","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/2579522a9e137af2e9fceda4aee5855042e9328d"},{"sha":"9e7cc9c17eb09b0f2b81993cbedb93e2bc79192f","author":{"email":"4737d94bfb8b7940843864fc531cf5f068ebec04@me.com","name":"Robert Jackson"},"message":"[BUGFIX release] Ensure local state can shadow attrs.\n\nWe initially intended to deprecate access to local state (ala proxying\nto attrs) at this location, but we have decided to hold off on that\ndeprecation until angle bracked component invocation is available.\n\nLater in the integration efforts, we added an AttrsProxy to handle most\nof this functionality for us (when using a View inheritor). In the\nfuture, the deprecation will almost certainly be added in the\n`AttrsProxy` (not `getRoot` hook).\n---\n\nPrior to this change local state could never use the same name as a\nvalue in `attrs` (because the `attrs` always \"won\").\n\nThe else case is still present, when a given template is not backed by a\nview/component instance.","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/9e7cc9c17eb09b0f2b81993cbedb93e2bc79192f"},{"sha":"2e505cd6785c2b51d937e674f2e6dffde3da89eb","author":{"email":"b1c1d8736f20db3fb6c1c66bb1455ed43909f0d8@rwjblue.com","name":"Robert Jackson"},"message":"Merge pull request #11572 from rwjblue/ensure-local-state-can-shadow-attrs\n\n[BUGFIX release] Ensure local state can shadow attrs.","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/2e505cd6785c2b51d937e674f2e6dffde3da89eb"},{"sha":"2b6e4b688b6dc4f27b1be49285a1a821a28ab594","author":{"email":"b1c1d8736f20db3fb6c1c66bb1455ed43909f0d8@rwjblue.com","name":"Robert Jackson"},"message":"Merge pull request #11570 from emberjs/11519-block-param-infinite-loop\n\n[BUGFIX release] Don’t force invalidation of block param streams","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/2b6e4b688b6dc4f27b1be49285a1a821a28ab594"},{"sha":"8a762df9f4474ed9c0e19ca9a5c1478fc59448d3","author":{"email":"b1c1d8736f20db3fb6c1c66bb1455ed43909f0d8@rwjblue.com","name":"Robert Jackson"},"message":"Merge pull request #11560 from joeruello/master\n\n[DOC Release] Mark transitionTo as public","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/8a762df9f4474ed9c0e19ca9a5c1478fc59448d3"},{"sha":"165cd58fab9c82b4b107e0f1e1906598c026d673","author":{"email":"b1c1d8736f20db3fb6c1c66bb1455ed43909f0d8@rwjblue.com","name":"Robert Jackson"},"message":"Merge pull request #11535 from jmurphyau/nested-sticky-qp\n\n[BUGFIX release] Sticky query params for nested and for dynamic routes","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/165cd58fab9c82b4b107e0f1e1906598c026d673"},{"sha":"7ffe8f70ee2b8a5c46e61c8e257e4157d141cc09","author":{"email":"f822051471957b7bbebb8ab088fe9bd6d14f4261@alum.mit.edu","name":"Edward Faulkner"},"message":"Remove unused import to fix jshint\n\nThis error sneaked into the repo due to #11574.","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/7ffe8f70ee2b8a5c46e61c8e257e4157d141cc09"},{"sha":"76359b76581bac20375dcecac73f95817a99fbd0","author":{"email":"0b40b374491a9d33ce3192c35cb80116802ee83a@gmail.com","name":"Stefan Penner"},"message":"Merge pull request #11575 from ef4/fix-unused\n\nRemove unused import to fix jshint","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/76359b76581bac20375dcecac73f95817a99fbd0"},{"sha":"78d03067055b96128c3c25ece10ff358c4764557","author":{"email":"f822051471957b7bbebb8ab088fe9bd6d14f4261@alum.mit.edu","name":"Edward Faulkner"},"message":"Added failing test for #11539","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/78d03067055b96128c3c25ece10ff358c4764557"},{"sha":"1fc7811a45dfb6184667364067203db4e2ff45dc","author":{"email":"f822051471957b7bbebb8ab088fe9bd6d14f4261@alum.mit.edu","name":"Edward Faulkner"},"message":"Fix view destruction inside outlets\n\nThis solution feels hacky and we need to discuss what code is really\nresponsible for view destruction. The htmlbars code that clears the DOM\ndoes not do view destruction, which leaves us in an awkward situation\nwhere the DOM is already removed but we need to destroy the view.","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/1fc7811a45dfb6184667364067203db4e2ff45dc"},{"sha":"88a0e98898980dda509af3b8bf2506497f58220c","author":{"email":"f4423ee8968f6158fcab7f642433e13a66b67bf6@gmail.com","name":"Steffen Brem"},"message":"[DOCS] Changed docs Ember.Route#modelFor to public\n\nShouldn’t the `modelFor` method of `Ember.Route` be public? Since the\ncode example is also using it in a public way.","distinct":true,"url":"https://api.github.com/repos/stefanpenner/ember.js/commits/88a0e98898980dda509af3b8bf2506497f58220c"}]}