You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 2, 2019. It is now read-only.
perhaps considering loading part of the data at a time? Rather than everything.
I feel like it would be better to have a small load every two months (how many users are curious about +/- two months) then have a huge load at the beginning, which encourages users to leave
The text was updated successfully, but these errors were encountered:
Perhaps we can start having pagination on the API or have a ?limit=20 type of parameter. Unless we already have this (@ethanresnick?). We can probably just load a subsection of the events data on load, and then load more if the user goes back more than a couple months? Since right now it's loading ~200 large events at once.
Yeah, we should definitely have pagination, and we don't now (except at one endpoint, I think). There's an open issue for it. Maybe we can figure out how to implement it efficiently when I'm next in NYC.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
perhaps considering loading part of the data at a time? Rather than everything.
I feel like it would be better to have a small load every two months (how many users are curious about +/- two months) then have a huge load at the beginning, which encourages users to leave
The text was updated successfully, but these errors were encountered: