hi guys, for those of you who are working with mob...
# orm-helpr
rein
08/13/2018, 9:14 AMhi guys, for those of you who are working with mobile apps in combination with Prisma, can I ask how you would model notifications? I have different types of notifications, such as likes, comments, follower, tag, ... but I m not sure what the best approach is to model those as data structure. Since there is still no interface type in Prisma, Im checking other options but id be curious to hear if anyone else here already has encountered/solved this problem. Cheers!
j
jaga_santagostino
08/13/2018, 9:55 AMGraphql has interfaces, so prisma does
r
rein
08/13/2018, 9:56 AMthats not how it works sadly
rein
08/13/2018, 9:56 AMrein
08/13/2018, 9:57 AMprisma is a proxy between your db and a graphql schema, it is not pure graphql, which means they’d need to implement interfaces before we could use them.
m
Moritz
08/13/2018, 9:57 AMHi, I've have been asking myself the same question. So far, I created a
NotificationNotificationTyper
rein
08/13/2018, 9:57 AM@Moritz thats exactly what I was doing atm
rein
08/13/2018, 9:57 AMhaha
rein
08/13/2018, 9:57 AMbut I have the same thoughts about the difficulty to maintain something like that
rein
08/13/2018, 9:58 AM@Moritz can I ask where you create your notifications? For example, I need to create a Notification when someone likes a post but to do that in the createLike resolver would make that resolver slower
rein
08/13/2018, 9:59 AMI wish there was a way to do that when the resolver has already returned
m
Moritz
08/13/2018, 9:59 AMHaha we have been asking ourselves the same questions 🙂
Moritz
08/13/2018, 10:00 AMSo far, I have been creating the notification in the likePost resolver asnycronously, i.e. call
ctx.db.createNotification(...)r
rein
08/13/2018, 10:01 AMyeah, plus, I want to check first to see if a notification already exists
m
Moritz
08/13/2018, 10:01 AMI think a very intersting new approach ist possible with https://github.com/prismagraphql/graphql-middleware
r
rein
08/13/2018, 10:01 AMhaha, I just tried that 😛
rein
08/13/2018, 10:01 AMbut it seems to trigger multiple times for me
rein
08/13/2018, 10:01 AMwhich is not very reliable
m
Moritz
08/13/2018, 10:02 AMThe lib is still pretty young 🙂
r
rein
08/13/2018, 10:02 AMwhen I log operationName/variables I see it pass by 3*4 times
rein
08/13/2018, 10:02 AMso I wouldnt want 4 notifications to be created
m
Moritz
08/13/2018, 10:02 AMIntersting... I havent played around with it much... Sounds like this might be worth an issue report.
Moritz
08/13/2018, 10:04 AMIf you check if the notification exists this should be a problem for now, should it? Its just ugly performance wise...
r
rein
08/13/2018, 10:04 AMyup
m
Moritz
08/13/2018, 10:04 AMBut yea please ping me if you find a neat solution, Id be eager to refactor mine 🙂
r
rein
08/13/2018, 10:04 AMill do so more experimenting
m
Moritz
08/13/2018, 10:08 AMGood luck 🍾
w
weakky
08/13/2018, 11:47 AMIf you need quick and immediate response, then what you need is optimistic update, but calling
createNotification()