Cache the history

[lmerriam]

Right now, if the user leaves the history to navigate to another section of the app, then returns to the history, they have to load the history again. If possible, it would be ideal to cache the currently visible history when the graph loads, so that the user can quickly switch between sections of the app.

[mpugach]

@lmerriam check on staging

currently it uses cache only if user has enough checkins to cover visible range

[lmerriam]

Thanks Max! It seems to be working well, could you clarify exactly what you meant here:

currently it uses cache only if user has enough checkins to cover visible range

[mpugach]

If the earliest checkin date is greater than visible start date then API call is preformed again. Same on other edge

[mpugach]

but the API calls are made with some room, so it tries to fetch more then visible

you can open the network tab in developer tools an play with it

the call look like this

[lmerriam]

Gotcha, sounds good.

One thing I should have been more explicit about:

As part of caching I was hoping we could save the user's position and visible trackables in the history. So that if I switch to the check-in, then switch back the the history, I'll return to the same position with the same visible charts and we won't have to reload any data (plus user gets the benefit of not losing their settings)

Is this feasible?

[mpugach]

I think it is.

[mpugach]

deployed to staging

[lmerriam]

Works fantastic for me!