agartha, thanks! I tried "# import * from 'prisma....
# prisma-whats-new
m
agartha, thanks! I tried "# import * from 'prisma.graphql'" but was not working
a
You can import explicit types, or root fields using
Query.*
,
Mutation.*
, or
Subscription.*
m
thanks really, I was fighting this for so much time now
👍🏻 1
a
Thank you for your feedback. I have created https://github.com/graphcool/graphql-import/issues/61 to improve on the documentation around this.
m
So do I need to write forwardTo('db') for every root field?
a
Yes
m
oh no.. so here we go again
a
That is the trade-off of being fully in control of the exposed schema
Here we go again?
m
thanks a lot for your help
I wish there was a simple "just forward the backend and add my this set of resolvers" command
a
You could wrap this in a little piece of scripting that takes an array of field names and generates the resolver object for you
m
but I don't know enough to understand why there isn't
a
We are always looking at ways to improve this
m
Sure, thanks for the work so far, it looks great
🙏🏻 1
a
I have created this issue for supporting your usecase: https://github.com/graphcool/graphql-binding/issues/37
m
thanks a lot. I am migrating from graphcool-framework, and was expecting that things would work the same in this regard (i.e. not having to care about the auto generated CRUD resolvers)
a
That's also the reason for creating this issue right away. The idea is that
prisma
+ `yoga`/`binding` should become feature similar to
graphcool-framework
, for lack of a better description
So filling these gaps is important for the overall experience
m
Great, thank you again.
🙏🏻 1