CATcher-org / CATcher-org/WATcher
Optimization of Github event API calls
Open
aspect-Performance
difficulty.Hard
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
**Currently**
Running multiple event API calls every second on Activity Dashboard,
4 event API calls every 5 seconds on Issue Dashboard
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Activity Dashboard and Issue Dashboard entry points and the GitHub event API polling they use. Measure the current request frequency, then determine how polling can be reduced while keeping both dashboards updated. Done means fewer event API calls without losing required dashboard updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- api, frontend, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100