bug: Enhance GitHub API Fetching Performance for Repo Stats

[JustinhSE]

Overview

We've identified a performance issue with our application's interaction with the GitHub API, specifically when fetching repository statistics. The current implementation is not retrieving data in a timely manner, which negatively impacts user experience and potentially affects our application's overall performance. This enhancement aims to optimize our API calls to github.com for repo stats, ensuring faster and more efficient data retrieval.

Tasks

• [ ] Analyze current API call implementation

  • [ ] Review existing code for GitHub API calls
  • [ ] Identify potential bottlenecks in the current approach
  • [ ] Document findings and share below

• [ ] Investigate GitHub API rate limits and best practices

  • [ ] Review GitHub API documentation for rate limiting policies
  • [ ] Identify any endpoints that might be causing delays
  • [ ] Research best practices for efficient API usage
  • [ ] Investigate caching strategies for frequently accessed data

[d-beloved]

@JustinhSE assign this to me pls

[d-beloved]

With the current approach to getting the repo data, if one of the promises fails, the function returns without resolving the remaining promises.

The new approach will make sure that all of the promises are settled before the response is sent to the component. A fallback number (1) is provided in case of promise rejection.

Also, a new approach to rendering the component is being explored where a call to GitHub API is made only once within a session, subsequent rendering of the page within the session will be fetched from the browser session.

These improvements will ensure that the data is always shown, improving the UX of the app and reducing the number of quota usage allowed by GitHub API.

cc: @JustinhSE @Namit2111