TooAngel / TooAngel/worlddriven
Caching of pull request data
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- JavaScript
- Stars
- 18
- Forks
- 15
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 5
Description
The frontend loads pretty slow, especially because a lot of data needs to be fetched from the github api.
Instead of fetching and calculating the data on each request, the data can be easily cached in the database backend. On webhooks and the regular worker this cache can be updated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the frontend requests that fetch and calculate pull request data from the GitHub API, then inspect the webhook and regular worker paths mentioned in the issue. Done means pull request data is served from a database cache and that cache is updated by both webhooks and the regular worker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100