We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've thought about adding proper caching of queries to make browsing historical data much snappier, after the first open.
The goal is to:
As a first step, I've considered adding query caching to aw-client-js such that queries are:
Should be a simple improvement, that could massively improve responsiveness and thus general UX of web UI, especially when browsing historical data.
I'm not sure what kind of cache expiry to add, but I might figure that out as I get going.
PRs:
The text was updated successfully, but these errors were encountered:
Now added basic caching, which gets invalidated on page reload. Significantly speeds up browsing around different dates.
Also found a bunch of requests that weren't needed, reducing the total number of requests significantly.
We can consider persisting the cache with some expiry mechanism in the future, to make it reload past dates superfast, even after page reloads.
Sorry, something went wrong.
No branches or pull requests
I've thought about adding proper caching of queries to make browsing historical data much snappier, after the first open.
The goal is to:
As a first step, I've considered adding query caching to aw-client-js such that queries are:
Should be a simple improvement, that could massively improve responsiveness and thus general UX of web UI, especially when browsing historical data.
I'm not sure what kind of cache expiry to add, but I might figure that out as I get going.
PRs:
The text was updated successfully, but these errors were encountered: