8 Commits

Author	SHA1	Message	Date
mattwr18	16d7e6c91a	Update notifications ... - create only one relationship by using merge, but do not update createdAt attribute/update test - order by updatedAt_desc	2019-09-13 20:14:47 +02:00
mattwr18	ce487f1e0f	Set notifications.createdAt only at creation ... - we should not be setting it every time a notification is created	2019-09-13 20:14:47 +02:00
roschaefer	98194ef54a	Follow @mattwr18's suggestions	2019-08-30 16:00:32 +02:00
roschaefer	cbcba8f08d	Follow @Tirokk's suggestion	2019-08-30 16:00:32 +02:00
roschaefer	c29ee5e3d3	Update notifications in place	2019-08-30 16:00:32 +02:00
roschaefer	994ab43950	Change the behaviour how notifications get created ... I think it makes more sense to update an existing notification in place. Ie. if there was already a notification, just mark it as unread so it ends up in the recipient's notification list again.	2019-08-30 16:00:32 +02:00
roschaefer	733c2d5ce1	All backend tests pass	2019-08-30 16:00:32 +02:00
Wolfgang Huß	af968461b6	Split handleNotificationsMiddleware in notificationsMiddleware and hashtagsMiddleware	2019-08-26 16:24:43 +02:00