Luc Vauvillier

Hi @Camji55, Take a look how nexus generates context types from `addToContext` user function calls. They walk through sources files and use the ts compiler to retrieve types and signatures:...

In the meantime, simpler version to inject custom types to NexusContext: ```typescript interface Token { sub?: string; iss?: string; aud?: string; exp?: number; iat?: number; name?: string; admin?: boolean; }...

Thanks a lot for this update. This is good news 👍 I think the community can help to maintain the current codebase to match future version of prisma and let...

The current plugin has lacks of control on what capabilities cruds exposes. Some nested operation are available (create, connect etc.) and it can open serious security issues. This results on...

Another workaround is to set `"skipLibCheck": true` in your typescript compilerOptions.

@HendrikJan I dont think this is faisable. nexus-prisma models are generated when you run `prisma generate`. All possibilities (read, create and update) should be generated at this time.

@jasonkuhrt Interesting. We can mix the "uniform" and "read-bias" using function/args. The default create case can be expressed without any arg: ```js const User = objectType({ name: User.$name(), description: User.$description(),...

Relations will also need an entry point to inject arguments (for filtering, ordering, pagination, etc.). These are more high level abilities but we need to keep it in mind. This...

Hi @SpaceK33z, There is another plugin done by @Sytten: https://github.com/Sytten/nexus-shield This is a well done @nexus/schema plugin but cannot be used directly by the framework. We are thinking about how...

After thinking more about how to merge, this cannot be just a wrapper. We have to keep an option to define rules in a separate "big" permission file. This will...