taras
commented
8 years ago Given the data-down actions-up principles combined with the idea that the route should handle actions related to updating the model, and the controller should handle actions from the user etc. It seems like the route should be maintaining the state of the count and offset parameters used to issue the store.findQuery command and the controller should know when user needs more data and invoke the actions in the route which should update the model with the next page of data. That being said, I'm just guessing and would be interested to see how other people do this.
This seems like the best option to me.
There is a very good infinity scroll addon available by @hhff. ember-infinity provides a {{infinity-loader}} component which shows the loading icon and triggers the model to load data and Route mixin that handles complexity related to asynchronously loading the data.
There is room to make this addon more data-down actions-up with Ember 2.0 concepts. One of the limitations that the current code has is that it's limited to 1 infinite scroll per page(I could be wrong about this). It also hides a lot of the logic related to querying data in the mixin and the component. I would like this functionality to be more exposed. Ember 1.13 introduced stateful helpers, which we could use to handle the asynchronous loading complexity and expose the loading state of the active query. This might make it possible for us to eliminate the need for Route Mixin and make the {{infinite-loader}} component much simpler.
With all of that said, I think ember-infiity is an excellent addon for doing Infinite Scroll today. Give it a shot :)
hhff
mattmazzola
Some background: I have an app built that loads the first page and I'm not sure how to add infinite scrolling to it. Given the data-down actions-up principles combined with the idea that the route should handle actions related to updating the model, and the controller should handle actions from the user etc. It seems like the route should be maintaining the state of the count and offset parameters used to issue the store.findQuery command and the controller should know when user needs more data and invoke the actions in the route which should update the model with the next page of data. That being said, I'm just guessing and would be interested to see how other people do this.
An alternative I could think of is to disregard using the model hook completely, and put all of the loading/updating logic into the controller.
Another option I had considered is that i could still split the logic between the route and controller, but I keep the route dumb and let it overwrite the model. Instead of rendering the model directly, I add another array in the controller which it knows to keep appending to whenever the model changes.
Anyways, I'm not sure if the above made sense, but infinite scrolling seems like a trendy UX thing these days and if there is a conventional way to do this in Ember it seems like a good thing to know!
Hope to hear your opinions!