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
The filtering process on generated trends is slow and inconvenient, requiring users to wait for charts to load before making adjustments.
i.e. when clicking these boxes on/off multiple times ☝️ or when changing the time period
Implement a more efficient filtering system that allows users to adjust filters independently of trend generation, possibly by caching results.
An alternative would be to allow users to preload all data and then filter locally on the client side.
This issue affects the usability of the platform, particularly when dealing with large datasets.
If you like this idea, please leave a 👍 or ❤️ reaction on this post to vote for it -- your votes and feedback help us prioritize what to work on next!
The text was updated successfully, but these errors were encountered:
Closing this issue, as this was mostly fixed. I have a todo for looking into debounced query updates / speeding up the insight UI in general.
Sorry, something went wrong.
No branches or pull requests
Feature request
Is your feature request related to a problem?
The filtering process on generated trends is slow and inconvenient, requiring users to wait for charts to load before making adjustments.
i.e. when clicking these boxes on/off multiple times ☝️ or when changing the time period
Describe the solution you'd like
Implement a more efficient filtering system that allows users to adjust filters independently of trend generation, possibly by caching results.
Describe alternatives you've considered
An alternative would be to allow users to preload all data and then filter locally on the client side.
Additional context
This issue affects the usability of the platform, particularly when dealing with large datasets.
If you like this idea, please leave a 👍 or ❤️ reaction on this post to vote for it -- your votes and feedback help us prioritize what to work on next!
The text was updated successfully, but these errors were encountered: