Does anyone know if there is a smooth way to extra...
# prisma-migratej
Josef Henryson
09/14/2019, 6:59 AMDoes anyone know if there is a smooth way to extract/export resolvers from GC and convert them into local resolvers calling Prisma?
t
tmoney
09/14/2019, 8:17 PMI used prisma-nexus and they have a cool SDL converter, and you can give it your endpoint, and they’ll give you all of the generated nexus resolver code. Made it go a lot faster:
https://nexus.js.org/docs/database-access-with-prisma
https://nexus.js.org/converter
j
Josef Henryson
09/15/2019, 8:58 AMCool, thanks! I will check it out! 🙂
Josef Henryson
09/15/2019, 12:07 PM@tmoney how did you handle the e.g. allUsers() in GC to users() in Prisma/Nexus? Did you rewrite your client app or did you add an alias in server?
t
tmoney
09/15/2019, 8:49 PMOn the front and back end we just aliased everything, so every query with
allUsersallUsers: userstmoney
09/15/2019, 8:50 PMAnd then moving forward we’re using just
usersj
Josef Henryson
09/16/2019, 7:20 AMgreat, thanks!
Josef Henryson
09/19/2019, 2:47 PM@tmoney sorry for taking your time again, but would you like to share how you created those aliases?
I have found a way, but it feels like a lot of coding, I was hoping for a simpler solution (backend that is)
t
tmoney
09/19/2019, 3:09 PMWe literally just did a ton of code changes… haha. We didn’t alias it from the backend, we aliased every query on the frontend
j
Josef Henryson
09/19/2019, 3:09 PMok, maybe that’s a better approach… my idea was to keep the client as is and only migrate the backend
t
tmoney
09/19/2019, 3:11 PMIf you can make that work that would be sweet. But I would also say, then you would probably end up keeping that convention in the frontend forever, which might also be its own confusing tech debt. So tradeoffs I suppose, but would definitely be much faster if you could completely alias it from the backend
j
Josef Henryson
09/19/2019, 3:12 PMTrue indeed, I will consider changing the client 🤔
Thank you for your input 🙏🏼