[FEATURE]: Improved GitHub API Fetching with IndexedDB Caching

[rudrakshtank]

Feature and its Use Cases

What does it do??

This update adds a browser-side caching layer using IndexedDB for GitHub API responses. The cache stores organization, repository, contributor, issue, and rate-limit data for a limited time, reducing repeated API calls and improving app responsiveness.

The update also improves the GitHub fetch flow by handling rate-limit information, supporting optional Personal Access Tokens, and reusing cached responses when valid data is already available.

What is the feaure

The feature is a client-side API caching and fetch optimization system for the Org Explorer app.

It includes:

• IndexedDB-based cache storage.
• One-hour cache expiration using TTL.
• Cached reads before making GitHub API requests.
• Automatic cache writes after successful API responses.
• GitHub rate-limit updates through a custom browser event.
• Support for authenticated requests using a Personal Access Token.
• Shared fetch logic through fetchWithCache.

Benefit

Users benefit because the app becomes faster, more stable, and more efficient.

Additional Context

No response

Code of Conduct

• I have joined the Discord server and will post updates there
• I have searched existing issues to avoid duplicates