feat: implement monthly spend calculation logic and metrics api (#196) #209
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey @MK-codes365 Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm. Thanks for contributing in OpenCode'25 ✨✨! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: #196
Key Changes
Unified Calculation: Automatically converts yearly, monthly, and weekly plans into a standard monthly spend.
Data Integrity: Filters out inactive subscriptions and handles invalid pricing/edge cases gracefully.
API Meta block: Updates GET /api/subscriptions to return total spending in a new meta field.
Decoupled Logic: Uses a dedicated metrics service for clean, testable calculation code.
Verified: Passed all logic tests for mixed-cycle subscriptions and zero-value entries.