Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[FEATURE]: Improved GitHub API Fetching with IndexedDB Caching

Open
  • Is something wrong?
#98 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github, javascript
Domain
api, database, frontend, performance

Research direction

The issue names no files, tests, or entry points. Start by locating the app’s GitHub API fetch flow and determine where organization, repository, contributor, issue, and rate-limit data are read and written; done means valid one-hour IndexedDB reuse, successful-response writes, rate-limit events, and optional token requests work.

Written by the indexing model from the issue text.

Description

enhancement
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
Dominant language
JavaScript
Stars
35
Forks
98
Avg merge
1d 21h
Merged PRs (30d)
9

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AOSSIE-Org/OrgExplorer

All issues in AOSSIE-Org/OrgExplorer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.