{"action":"created","issue":{"url":"https://api.github.com/repos/hhff/ember-infinity/issues/150","repository_url":"https://api.github.com/repos/hhff/ember-infinity","labels_url":"https://api.github.com/repos/hhff/ember-infinity/issues/150/labels{/name}","comments_url":"https://api.github.com/repos/hhff/ember-infinity/issues/150/comments","events_url":"https://api.github.com/repos/hhff/ember-infinity/issues/150/events","html_url":"https://github.com/hhff/ember-infinity/issues/150","id":147468027,"number":150,"title":"Ember Infinity on 2 or more nested routes","user":{"login":"hhff","id":2865404,"avatar_url":"https://avatars.githubusercontent.com/u/2865404?v=3","gravatar_id":"","url":"https://api.github.com/users/hhff","html_url":"https://github.com/hhff","followers_url":"https://api.github.com/users/hhff/followers","following_url":"https://api.github.com/users/hhff/following{/other_user}","gists_url":"https://api.github.com/users/hhff/gists{/gist_id}","starred_url":"https://api.github.com/users/hhff/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hhff/subscriptions","organizations_url":"https://api.github.com/users/hhff/orgs","repos_url":"https://api.github.com/users/hhff/repos","events_url":"https://api.github.com/users/hhff/events{/privacy}","received_events_url":"https://api.github.com/users/hhff/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-04-11T15:37:50Z","updated_at":"2016-07-11T15:18:52Z","closed_at":null,"body":"@venkz identified a problem with using multiple instances of Ember Infinity on nested routes.\r\n\r\nWith a `parent/child` architecture, triggering a `loadMoreAction` on the parent route will be caught by the child route.  This is because Ember fires route actions from the most-active leaf of the router, rather than the corresponding route for the template.\r\n\r\nThis was unexpected behavior for me, and I'm still working around nice solution for Ember Infinity.\r\n\r\nWould love to hear any thoughts here.\r\n\r\nWanted to open this here to track progress.\r\n\r\nFor Now, if you're doing this - please use this pattern:\r\nhttps://github.com/hhff/ember-multi-infinity-scroll/commit/cfba20b78316266ea170136e8fd11a7813cc7b65\r\n\r\nRelated Issue:\r\nhttps://github.com/emberjs/ember.js/issues/13288"},"comment":{"url":"https://api.github.com/repos/hhff/ember-infinity/issues/comments/231766688","html_url":"https://github.com/hhff/ember-infinity/issues/150#issuecomment-231766688","issue_url":"https://api.github.com/repos/hhff/ember-infinity/issues/150","id":231766688,"user":{"login":"Blackening999","id":2836887,"avatar_url":"https://avatars.githubusercontent.com/u/2836887?v=3","gravatar_id":"","url":"https://api.github.com/users/Blackening999","html_url":"https://github.com/Blackening999","followers_url":"https://api.github.com/users/Blackening999/followers","following_url":"https://api.github.com/users/Blackening999/following{/other_user}","gists_url":"https://api.github.com/users/Blackening999/gists{/gist_id}","starred_url":"https://api.github.com/users/Blackening999/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Blackening999/subscriptions","organizations_url":"https://api.github.com/users/Blackening999/orgs","repos_url":"https://api.github.com/users/Blackening999/repos","events_url":"https://api.github.com/users/Blackening999/events{/privacy}","received_events_url":"https://api.github.com/users/Blackening999/received_events","type":"User","site_admin":false},"created_at":"2016-07-11T15:18:52Z","updated_at":"2016-07-11T15:18:52Z","body":"@hhff \r\nyep, I've checked the opportunity to call \"private\" method which works :)\r\nhope will have time for PR since it's really easy thing to do.\r\nInstead of using mixin - use a service, and make it mandatory to define the method for handling infinity load with further calling a public method on that service. The explicit method will allow to do any side-change during infinity load update.\r\nThe issue is, I don't think you'll want merge it since a lot of users already relies on mixin :\\\r\n"}}
{"actor":{"display_login":"Blackening999"}}