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

[Feature request] Cache results #39

Open
matthewruzzi opened this issue Dec 9, 2021 · 3 comments
Open

[Feature request] Cache results #39

matthewruzzi opened this issue Dec 9, 2021 · 3 comments

Comments

@matthewruzzi
Copy link

It would be great if there was a way to cache the results since they take a long time to generate and require a lot of API calls.

@payne911
Copy link
Collaborator

payne911 commented Dec 11, 2021

Yeah, I'm aware. The Export CSV button was specifically introduced as a quick-fix to this.

Unfortunately, I'm not entirely sure how to approach this problem given that the tool is ran as a stateless static website (because that is provided for free by GitHub).

@matthewruzzi
Copy link
Author

Could the results be cached in the local browser cache?

@payne911
Copy link
Collaborator

payne911 commented Jul 4, 2023

Essentially, yes.
Maybe octokit somehow already has some caching capability: that would have to be investigated.
But all in all, given the limited time I can give to this project, I'm not sure I will personally explore how to implement this feature in the near future. Others are welcome to try, though!

The main use-case I can see this being useful for is when the search ends up being interrupted, and one has to refresh the page to start again: if all calls were cached, it would almost immediately restart from where it left off.
This mostly only happens on enormous scans, and would probably represent a decent amount of coding, though.

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