ergoplatform / ergoplatform/explorer-backend
Request caching
Open
A-backend
C-feature
P1-high
- Dominant language
- Scala
- Stars
- 23
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Entries can be invalidated when a new block is applied.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating request caching and the path that applies a new block, then determine which entries should be invalidated. Done means the cache reliably invalidates the affected entries whenever a new block is applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend, blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100