https://www.prisma.io/ logo
Join Slack
Powered by
trying to break it down to the simplest way I can ...
# orm-help
c
trying to break it down to the simplest way I can explain
h
are you using prisma client or bindings?
c
I am using bindings in the parent
I can use either one in the child
h
Mixing both is not a good thing 😉
c
why?
prisma client is nicer to use but the issue is it always queries everything
and as I read in the discussion, prisma client is not meant to replace prisma bindings and should be used for different use cases...
there was a big long thread about it either on the forums or github I don't remember
h
But lets solve your current problem, maybe DM would be better as I can ask for more info
Also, feel free to give suggestion in the RFC
c
is this basically allowing you to pass info into prisma client
?
so you don't query everything/
?
h
Yes, I don't know that is the part of the RFC. cc @schickling may help here
c
the nicest thing would be some sort of helper function
to easily extend the 
info
object to add fields to it
like if the user requests a certain query, I can say, I want to request that query but always add 
ID
when it goes to prisma
h
I think you should comment about this in the RFC. 🙂
c
ok, I can look at it later
h
Current problem has been resolved in a DM. Tl;DR addFragmentToInfo from graphql-bindings will solve this
2 Views
Open in Slack
PreviousNext
Powered by