Working on an adaptator could be a game changer when building backoffices
v
Victor
05/18/2018, 4:47 PM
If it supports graphql and you give it your database endpoint ( taking into account security ) and you should be ready to go
c
cmcinroy
05/18/2018, 5:01 PM
Wow. That looks great!
w
weakky
05/18/2018, 5:27 PM
It does support graphql, although you either have to follow an arbitrary semantic, or make your own adaptator. I think accessing the prisma endpoint directly wouldn't be that stupid for backoffice purposes. Most of the stuff you'll be doing are fetchAll() and upsert mutations anyway. They already have an adaptater for graphcool, that'd be sick if we could make it work with prisma schemas
n
nilan
05/18/2018, 5:29 PM
what do you mean with arbitrary semantic?
w
weakky
05/18/2018, 5:32 PM
I was about to edit. I mean arbitrary graphql schema convention (about the way you need to name your fields, the inputs they take etc etc)