-
Notifications
You must be signed in to change notification settings - Fork 0
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
Notification dropdown #1152
Notification dropdown #1152
Conversation
Added pg script.
Added WebCommentNotification to send to the client.
I don't think this should close 622, since it's likely just the backend work, right? |
No, but we can open it again. |
Return empty list when no notifications are found.
For some reason a single access check test is failing on the CIs, it runs fine locally. Once I'm done adding all the remaining tests I'll check what's wrong with it. |
list instead of a map of lists. Easier to sort on the frontend and distinguish between them as well. Added notifications to test. Added tables to pgsql script. Added endpoints to swagger-ui.
This PR is a bit large for my taste. In the future try to keep it smaller. |
data = assign({}, data, { | ||
sectionVersion: 1 | ||
}) | ||
data = assign({}, data); |
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.
Closes #622.
Added notifications for the following actions:
Api docs:
Check and uncomment notifications in /documents/src/main/resources/documents/db/h2/migration/V11__change_user_notification.sql to test.
Other: