feat: daily-stacked-notifications #2132
Draft
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
m0wer
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Added a daily stacked notifications feature that sends users a summary of their stacking and spending activity from the previous day. Users can enable/disable this feature in their settings.
Closes #1751.
Screenshots
None - server-side feature with minimal UI changes (just a checkbox in settings)
Will add some once I get a test setup fully working.
Additional Context
The implementation includes database migration, scheduled PgBoss job that runs at 1:15 AM CT, and comprehensive notification handling.
I'm not sure about how migrations are run in production or about the preferred way of scheduling PgBoss jobs.
Checklist
Are your changes backwards compatible? Please answer below:
Yes, fully backwards compatible. Feature is enabled by default but users can opt-out.
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
6/10 - Tested the notification generation and delivery logic with manual job triggers couldn't yet find a simple test setup with real data to see the notification happening. Verified UI integration in settings page.
For frontend changes: Tested on mobile, light and dark mode? Please answer below:
Yes, checkbox in settings works correctly on mobile and in both light/dark modes.
Did you introduce any new environment variables? If so, call them out explicitly here:
No new environment variables introduced. Uses existing VAPID settings for web push notifications.