13 Commits

Author	SHA1	Message	Date
roschaefer	978347ba7b	Tell github-linguists to ignore snapshots	2019-11-16 20:09:05 +01:00
roschaefer	cbc547a86b	refactor: small refactoring for readability ... @KapilJ your solution is right now the best solution, I think. Probably the ideal solution would be if we could implement the `CreateComment` resolver in such a way that it is doing eager loading of the `comment->post->author` relationship and resolving a commment object which has the required objects all set. Then you wouldn't have to refetch all the stuff. But I think this is OK for now 👍	2019-10-31 16:11:05 +01:00
Kapil Jain	b4a9e3e551	add software tests for two notifications bug	2019-10-31 05:08:15 -04:00
Kapil Jain	c21ad2244f	add software tests for two notifications bug	2019-10-30 22:03:52 -04:00
Kapil Jain	063ff17d8b	add software tests for two notifications bug	2019-10-30 20:39:50 -04:00
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