Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Triggering events on paginated remote #216

Open
typeoneerror opened this issue Feb 24, 2017 · 3 comments
Open

Triggering events on paginated remote #216

typeoneerror opened this issue Feb 24, 2017 · 3 comments

Comments

@typeoneerror
Copy link

typeoneerror commented Feb 24, 2017

I've run into a situation where I want to know when the paginate-remote-array starts loading in fetchContent and when it ends. I'm not sure with the current execution that there's a way to then() the promise that is created internally.

There seems to be two places where PaginatedRemoteArrays are created. The initial load is created in the remote mixin in findPaged. This first call is certainly thenable, but successive calls are then created inside the paginated-remote-array class do not have a mechanism for observing or then'ing.

My questions:

  1. how can we redesign this system so it uses a single source for the promise, making all promises consistently then'able.
  2. should we add additional triggers to the remote-array instead?
@typeoneerror
Copy link
Author

Similar issue here: #88

@lancedikson
Copy link
Contributor

@typeoneerror, have you found any workaround?

@lancedikson
Copy link
Contributor

@typeoneerror, I've found a solution for it. Look at the comment: #88 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants