marigold-dev / marigold-dev/tzproxy
TTL per route
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Allow to set TTL for different routes:
Check what we are using for cache first:
https://github.com/fraidev/go-echo-cache
https://github.com/coocood/freecache
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 cache integration and route-handling entry points in the repository. Review the linked go-echo-cache and freecache projects before deciding how route-specific TTLs should fit the existing design. Done means different routes can use different TTL values and the behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100