Repository navigation
Cache-Control decoration on GET /api/v1/campaigns, claims, audit logs #240
Description
Activity
Hello maintainer, I have reviewed the issue and I am ready to work on it. I have experience with Typescript, PplgSQL and Python development, also audit logs management and HTTPs endpoints utilization. Let me help you!
I participated in the previous GranfFox Campaign (First Ofifcial Campaign) I will take over and deliver a HQ PR.🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!
@Kend07's PR #369 was approved and merged by @kilodesodiq-arch.
🏆 @Kend07: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (131 total points). Track your full progress on GrantFox.
👏 Great work, @Kend07! Keep contributing to ChainForgee.
Problem Statement. The HTTP-cache interceptor exists but only fires from the
controller decorator side. List endpoints haven't been adorned.
Why it matters. Dashboards refetch the same campaign list every minute. A correct
max-age=30saves significant Prisma load.Technical Context.
@HttpCacheTtl(30)and@SkipHttpCache()decorators exist;campaign, claim, audit-list endpoints do not use them.
Expected Outcome. All
findAll-style GET endpoints decorated; anX-Edge-Cache-Statusreturned in non-prod for debuggability.
Acceptance Criteria.
GET /campaignsreturnsmax-age=30after first call.X-Edge-Cache-Status: hit.Files or modules likely to be affected.
src/campaigns/campaigns.controller.ts,src/claims/claims.controller.ts,src/audit/audit.controller.ts.Dependencies. #31 (pagination).
Difficulty. Easy
Estimated effort. S
Backlog item #32 from `docs/maintainer-issue-backlog.md.