-
-
Notifications
You must be signed in to change notification settings - Fork 23.2k
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
fix: total commits count #15
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good otherwise 💯
@anshumanv Hi, i just did some performance testing and found out that to fetch all of your profile's commits it took over ~4 seconds to get back the response.. So do you have any ideas of improving the speed? One thing i can do is have a option for specifying if users want to fetch all of the commits like |
This is definitely one but I'm not sure of cases when a user would want to limit their count, but can't think of anything else atm. This seems the best choice to me. 👍 |
You can give it a count param too, for the number of queries i.e no of years. |
Why not change the default text to "Current Year Commits" or "Commits for Last 365d" or something. With an option for "Total" commits along with a statement that there's a performance concern in doing such.... |
is this fixed and merged to master branch? |
No @TheAshwanik meanwhile you can hide the totalCommits stats if you want with |
Don't worry about rank it's not something that shows how skilled or how good you are. its just a rank for github activity. just like contribution chart. also fix would come up in this week, we need to fix the rank algo too because its biased currently |
Yes. Absolutely. |
* Add cache to function response * Lowered cache-control maxage to 5 min * Changed cache control directives to public, max-age * Added cache-control to pin.js
Fixed in #211 |
So as i mentioned in #14 that github api only return commits of 1 year max. what i did is that fetched all user years and then looped through that and made a graphql request for each year
TODO: perf improvement?