fix: use unified metrics cache in compare endpoint (#811)#1219
Conversation
|
@Vaibhavi-14shetty is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel. A member of the Team first needs to authorize it. |
GSSoC Label Checklist 🏷️@Priyanshu-byte-coder — please apply the appropriate labels before merging: Difficulty (pick one):
Quality (optional):
Validation (required to score):
|
There was a problem hiding this comment.
Thanks for your first PR on DevTrack! 🎉
A maintainer will review it within 48 hours. While you wait:
- Make sure CI is passing (type-check + lint)
- Double-check the PR description is filled out and the issue is linked
- Feel free to ask questions in Discussions if you need help
If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!
|
Hello @Priyanshu-byte-coder, I’ve completed the changes for this issue #811 |
a1193d8
into
Priyanshu-byte-coder:main
|
🎉 Merged! Thanks for contributing to DevTrack. If the project has been useful to you, a ⭐ star on the repo is the easiest way to support it — it helps DevTrack get discovered by more developers. Keep an eye on open issues for your next contribution! |
Summary
This PR refactors the compare metrics endpoint to use the unified caching implementation from
metrics-cache.ts, ensuring consistent cache usage across metric-related APIs and eliminating redundant or endpoint-specific caching logic.Closes #811
Changes Made
src/app/api/metrics/compare/route.tsto use the shared metrics cache instead of local or duplicated caching logicsrc/lib/metrics-cache.tsto support unified cache access for compare endpoint usageHow to Test
Checklist