Internal Notification Factory

[teeschima]

CLOSES #175 [Backend] Implement NotificationService.create() — Internal Notification Factory

Background

Other modules (markets, predictions, leaderboard) need to create notifications for users. A shared NotificationService.create() method acts as the internal factory.

Changes Made

• ✅ Implement NotificationService.create(userId, type, title, message, metadata?)
• ✅ Create NotificationType enum with: MARKET_RESOLVED, PAYOUT_READY, RANK_CHANGED, COMPETITION_STARTED, COMPETITION_ENDED, PREDICTION_WON, PREDICTION_LOST
• ✅ Call create method from MarketsService.resolveMarket(), PredictionsService.claimPayout(), and LeaderboardScheduler.recalculateRanks()
• ✅ Add proper module imports and dependency injection
• ✅ Update unit tests to use new enum values
• ✅ All enum types are documented
• ✅ NotificationService is exported and usable from any module

Acceptance Criteria

• NotificationService is exported and usable from any module
• All enum types are documented
• Called correctly from at minimum 2 other services
• Unit tests written for the factory method

Testing

Run the step-by-step testing process provided in the implementation to verify all functionality works correctly.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
insight-arena-4rll	Ready	Preview, Comment	Mar 27, 2026 11:25am

[drips-wave]

@teeschima Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits