-
Notifications
You must be signed in to change notification settings - Fork 0
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
F5 reload spends 2 requests available #14
Comments
Sadly this is expected behavior at the moment. Each time you load, reload or update the search parameters, one request is sent to GitHub’s API. The best we could do is to only spend 1 request to fetch the repository list on load/reload, but due to the way that stats need to be fetched, we need to spend a second request initially. I’m looking for a way to “cache” these stats at build time and keep them static for upcoming requests, this way, we could fire an update weekly and have decent update time, however, there’s no easy way ATM for this. Will keep this open, I’m thinking on making the necessary changes for static first loads when Nuxt v3 is released. Thanks for the heads up! |
Quick follow up... It seems that I misconfigured the project... I was hoping to provide a full static ( According to NuxtJS Docs, the
So, we are already expecting |
I was looking for something simple to contribute 😅 , do you have something on your mind? |
I have some ideas locally. If you’re free tonight we could spin up a simple pair programming session to further discuss what I got in mind. PS: Here are my thoughts:
|
This week I have tons of pending job, what about next week? 😄 |
Sure thing, I’ll keep trying out, maybe push tonight a new branch with experimental changes |
I don't know if it is the expected behaviour or a bug.
Before F5:
![imagen](https://user-images.githubusercontent.com/36722374/102800791-f9717c00-4379-11eb-9d00-6f9f30b7b93d.png)
After F5:
![imagen](https://user-images.githubusercontent.com/36722374/102800856-127a2d00-437a-11eb-957f-628d6823d2ef.png)
The text was updated successfully, but these errors were encountered: