graphprotocol / graphprotocol/indexer
Configurable timer durations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
The Agent has numerous timed, cyclic operations with hard-coded durations, but indexers may want to customize their frequency.
Therefore, exposing those timer durations in configuration would be beneficial.
We can use the current, hard-coded durations as a default for all timers.
Contributor guide
No contributing guide indexed for this repository
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 locating the Agent's hard-coded durations for timed, cyclic operations and the existing configuration entry points. Identify each timer that indexers may need to customize, retain the current durations as defaults, and verify that configuration can control their frequencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100