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	67d68db231	Update post resolver to fix embarrasing bugs ... - when a user updates a post, we should not override every property in our database with the new params, since we have read-only properties like createdAt that we don't want to go deleting aimlessly.	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	2a3e6ad76f	Alternative solution for #1494	2019-09-13 20:14:47 +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	643d175ef6	Implement notifications resolver	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