-
Notifications
You must be signed in to change notification settings - Fork 881
feat: add notification preferences database & audit support #14100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Meticulous spotted zero visual differences across 468 screens tested: view results. Expected differences? Click here. Last updated for commit 5d683d4. This comment will update as new commits are pushed. |
76d4ca5
to
85ec862
Compare
85ec862
to
8333dcb
Compare
8333dcb
to
93a92d6
Compare
2105aa4
to
c4b8b31
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
User's have NotificationPreference
which relates to NotificationTemplate
. But only admins/owners can setup NotificationTemplate
?
coderd/database/migrations/000237_notification_preferences.up.sql
Outdated
Show resolved
Hide resolved
coderd/database/migrations/000237_notification_preferences.up.sql
Outdated
Show resolved
Hide resolved
coderd/database/migrations/testdata/fixtures/000237_notifications_preferences.up.sql
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review @Emyrk 👍
User's have NotificationPreference which relates to NotificationTemplate. But only admins/owners can setup NotificationTemplate?
Correct; notification templates only store system-level templates right now; the design will evolve to allow operators to create their own notification templates.
coderd/database/migrations/000237_notification_preferences.up.sql
Outdated
Show resolved
Hide resolved
coderd/database/migrations/000237_notification_preferences.up.sql
Outdated
Show resolved
Hide resolved
coderd/database/migrations/testdata/fixtures/000237_notifications_preferences.up.sql
Outdated
Show resolved
Hide resolved
6ea0336
to
2cc690c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments below but I don't need to review again.
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
… kind Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
Signed-off-by: Danny Kopping <[email protected]>
2cc690c
to
c744d33
Compare
Signed-off-by: Danny Kopping <[email protected]>
Part of coder/internal#19
NOTE: I used Graphite for this, but it's got too many sharp edges. I'm reverting to manually managing these branches.
This implements the foundation of the feature - namely the database changes, along with auditing support and RBAC - all used in upstack PRs. I initially had these 3 elements in separate branches, but it became too much of a PITA to maintain with Graphite. In the future I'll start with one big branch and decompose before review time instead of decomposing ahead of time.
THIS PR MUST BE MERGED LAST!