Skip to content

Conversation

@Christinarlong
Copy link
Contributor

@Christinarlong Christinarlong commented Feb 10, 2026

The purpose of the NotificationSource/NotificationTemplateSource imo is more to represent a unique notification being sent through the platform. Idt it's really specific to templates so renaming. Also combining it with Category to reduce enum spaghetti.

Going to use NotificationSource later for the threading models

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Feb 10, 2026
@Christinarlong Christinarlong changed the title chore(notifications): Combine template and category chore(notifications): Rename NotificationTemplateSource to NotificationSource and combine source + category Feb 10, 2026
@Christinarlong Christinarlong marked this pull request as ready for review February 10, 2026 23:00
@Christinarlong Christinarlong requested a review from a team as a code owner February 10, 2026 23:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant