-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forward plugin fields in t.crud and t.model #584
Comments
Hey @gabrielcolson thanks for this idea. Looks good to us too. Bit of an experiment to see if this could lead to unintuitive fields on model/crud. We’re not sure how hard this issue will be to implement but we would like to see it land this quarter. If by the end of February we think this might not make it from our side your contribution would be more than welcome. |
@jasonkuhrt was this issue removed from the This Quarter board in favor of something else, or is it just not a priority? I'm not sure we really need to have the plugin attributes added to the generated type, though that would be nice. Personally i would settle for a the ability to pass an array of middleware that would wrap the generated resolver. Not having any ability to intercept the request is a massive pain point.
|
This is a big bummer at the moment. You basically have to choose between using nexus prisma or any other plugin (authorize, query complexity, custom ones, etc). A lot of the value in code-first schema construction are these plugins that allow abstracting common schema structure and functionality. The fact that the prisma plugin cuts you off from using the rest of them is really limiting. |
Hey everyone, we've just made it possible to use external field plugins into Nexus Prisma thanks to #687. It'll be available in the next release of |
@Weakky this is great, thank you! Do you have an ETA on the release and what version it will be? This is directly impacting a project we have progress at the moment. |
@jcloutz-radix canary today |
We've just released |
@Weakky thank you! I am trying to give it a test run using the blog example and it won't generate the nexus schema types. When i downgrade to
package.json
|
Sorry about that I forgot to update the examples. Crud is now behind a feature flag. |
@Weakky that did the trick! |
Can I please to add https://www.nexusjs.org/#/tutorial/chapter-5-persisting-data-via-prisma Should I type:
? Ok. I found example with:
https://github.com/graphql-nexus/examples/blob/master/plugin-prisma/api/app.ts |
Hey,
It would be nice to be able to access the "dynamic fields" created by the other plugins in
t.model
andt.crud
.Example with the Field Authorize Plugin:
I would be happy to contribute if you need me to. This is an important feature to me because I would like to get rid of Graphql Shield ASAP.
PS: I know there is an opened issue about the Field Authorize Plugin but I wanted to extend it to play nice with any other plugin.
The text was updated successfully, but these errors were encountered: