user
07/20/2018, 1:41 PMRoy
07/20/2018, 2:03 PMwieseljonas
07/20/2018, 2:04 PMwieseljonas
07/20/2018, 2:05 PMwieseljonas
07/20/2018, 2:06 PMRoy
07/20/2018, 2:06 PMwieseljonas
07/20/2018, 2:06 PMRoy
07/20/2018, 2:08 PMwieseljonas
07/20/2018, 2:09 PMwieseljonas
07/20/2018, 2:09 PM<https://myServer.herokuapp.com/bf-heroku/dev>
wieseljonas
07/20/2018, 2:10 PMwieseljonas
07/20/2018, 2:11 PMwieseljonas
07/20/2018, 2:11 PMJim
07/20/2018, 2:12 PMRoy
07/20/2018, 2:16 PMRoy
07/20/2018, 2:21 PMterion
07/20/2018, 2:30 PMuser
07/20/2018, 3:50 PMPedro Jardim
07/20/2018, 6:48 PMbrandon
07/20/2018, 8:50 PMERROR: Whoops. Looks like an internal server error.
brandon
07/20/2018, 8:50 PMbrandon
07/20/2018, 8:51 PMterion
07/21/2018, 11:01 AMterion
07/21/2018, 12:36 PMLink
. It has a field that depends on some data of Link. Let's assume that Link->link
depends on Link->order
. So, to resolve Link->link
field I need to always have order
on selection. When I forward requests to prisma
it returns only subset of data that is requested by client and if client requests links { link }
prisma will only return link
field from db. I need to force it to get order
too. @nilan pointed out in issue that it can be achieved via fragment in resolver, but it doesn't work that way. How to do this?Haider Malik
07/22/2018, 3:19 AM{
"error": "Could not connect to websocket endpoint <wss://us1.prisma.sh/haider-malik-c1556d/hackernews-clone/dev>. Please check if the endpoint url is correct."
}
drizzie
07/22/2018, 5:04 PMdrizzie
07/22/2018, 5:12 PMChris
07/22/2018, 8:15 PMKalmuraee
07/23/2018, 8:51 AMFran Dios
07/23/2018, 11:21 AM