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

Caching #50

Open
nerocui opened this issue May 14, 2023 · 3 comments
Open

Caching #50

nerocui opened this issue May 14, 2023 · 3 comments

Comments

@nerocui
Copy link
Collaborator

nerocui commented May 14, 2023

All network calls should be cached for faster UX

@RokeJulianLockhart
Copy link

RokeJulianLockhart commented Aug 20, 2024

#50 (comment)

@nerocui, if so, there shall need to be an obvious and ever-present way to clear the cache manually. A refresh button, perhaps?

@nerocui
Copy link
Collaborator Author

nerocui commented Aug 20, 2024

Yeah that's been on my mind too. My currently WIP displays the cached value and always makes a new call anyway. So the cache is more served as a way to have faster initial UI. So this way I need to let user know the initial UI is "loading" while I fetch for latest data. Perhaps it could be more relaxed on things that don't changes much, like repo name or issue names.

@RokeJulianLockhart
Copy link

#50 (comment)

@nerocui, I like that UX a lot more. It means that whilst it's loading, I can clearly see that, but also not waste time if it's something that I know hasn't changed.

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