Ehmi/lb/notification backend #791
Open
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.
This pull request introduces notification management features with real-time updates and UI enhancements, mainly by implementing new backend models for notifications, donations, and users, and updating project configuration and task tracking. The changes lay the groundwork for a more robust notification system, including user preferences and service architecture.
Backend model implementations:
notification.model.jswith a comprehensive schema for notifications, supporting multiple types, statuses, metadata, expiration, and user notification preferences for channels, types, and do-not-disturb settings.donation.model.jsto handle donation records, including amount, currency, donor email, Stripe charge ID, status, and receipt URL.user.model.jsto expand user schema with status, roles, block message, timestamps, and indexing for efficient queries.Project configuration and tooling:
.dockerignoreto exclude.envfiles for better security and cleaner Docker builds.