Hey there! We're having an N+1 issue with nexus-prisma on nested queries. It seems like nexus-prisma is resolving fields using findOne here (snippet from nexus-prisma builder.ts):

const fieldConfig = this.buildFieldConfig({
          field,
          publisherConfig,
          typeName,
          resolve:
            field.outputType.kind === 'object'
              ? (root, args, ctx) => {
                  const photon = this.getPhoton(ctx)
                  return photon[lowerFirst(mapping.model)]
                    ['findOne']({
                      where: { [idField.name]: root[idField.name] },
                    })
                    [field.name](args)
                }
              : undefined,
        })

Which is causing hundreds of queries for a moderately-sized three-level nesting query. The generated queries when running this query directly from prisma look fine, so we're pretty certain that this field resolver is causing the problem.

We do rely on nexus for generating types, so in lieu of moving away from it, we're looking to see if there's a possible workaround that would let us run the query directly. If anyone knows how we can do this, an example would be incredibly appreciated!

Has anyone been able to use

nexus

with

apollo-client

and

apollo-link-state

to handle client local state?

eta on when this the tutorial will be back up? https://github.com/prisma/prisma2/blob/2.0.0-preview024/docs/tutorial.md

Hey, is there a way to connect a client created with GraphQL-CLI into Nexus in the same way Nexus-Prisma connects? Meaning able to pass through and extend.

This would be extremely helpful, of if someone can point me in the right direction to do it myself.

Question 2, how can I implement graphql-sequelize into a

t.connectionField(

${TypeNames.name}s_connection

, {             type: TypeNames.name,             resolve: async (root, args, ctx, info) => {             }         });

Having issues deploying a GraphQL Server to Zeit’s now service with

nexus

. Local development (via nodemon) works without a hitch. Might anyone know why? I couldn’t find any examples for GraphQL Yoga & Nexus in JS with now deployment. Getting the 502: BAD_GATEWAY Code: 

NO_STATUS_CODE_FROM_FUNCTION

error.

// Packages
import { GraphQLServer } from 'graphql-yoga'
import { nexusPrismaPlugin } from 'nexus-prisma'
import { makeSchema } from 'nexus'
import { PrismaClient } from '@prisma/client'
// Types & Resolvers
import types from './types'
import resolvers from './resolvers'

const prisma = new PrismaClient()

const client =
	process.env.NODE_ENV === 'development' ? process.env.CLIENT_DEV : process.env.CLIENT_PRO
const server =
	process.env.NODE_ENV === 'development' ? process.env.SERVER_DEV : process.env.SERVER_PRO

new GraphQLServer({
	schema: makeSchema({
		types: { ...types, ...resolvers },
		plugins: [nexusPrismaPlugin()],
		outputs: {
			schema: __dirname + '/schema.graphql'
		}
	}),
	context: ctx => ({ ...ctx, prisma })
}).start(
	{
		port: 4000,
		cors: { credentials: true, origin: [client] }
	},
	() => console.log(`🚀 Server ready at: ${server} ⭐️`)
)

now.json file

{
  "version": 2,
  "builds": [
    {
      "src": "src/index.js",
      "use": "@now/node-server"
    }
  ],
  "routes": [
    {
      "src": "./*",
      "dest": "src/index.js"
    }
  ]
}

So any know how to do testing with Jenkins on Nexus?

Is there a way to turn the NexusSchema into an executable schema? We already have tests written for a schema first approach, but we switched to Nexus and don't want our test coverage to go down.

@martin This is the same with me, I managed to deploy mine to Netlify but unsure how to access the my graphQL api from the netlify url they made

Hello 👋 If I am building a production application with Nexus and Prisma, which combination should I use? • Nexus Future & Prisma 2 • Nexus Schema & Prisma 2 Thank you

Has anyone gotten Nexus running on AWS Lambda (or any serverless environment) ?

Hmmm… has anyone gotten Nexus running in Heroku using the instructions in their tutorial? I am getting

app boot timeout

errors.

Hi guys. is there a way to do include auth logic inside nexus crud operations?

nextjs example?

It would be nice to show some loading indicator during installing dependencies

Can anyone help with this issue? https://github.com/graphql-nexus/nexus-schema-plugin-prisma/issues/419

It refers to the

did you forget to import a type to the root query

error

Is there a way to add a callback to a

crud

operation? I want to publish to a pubsub channel on update. Do I need to recreate the operation manually in order to do this?

When creating your own mutation, is there a way to automatically generate the args based on an auto-generated CRUD operation? For example, if I have a

Product

model I get an auto-generated

prisma.createProduct

. If, however, I want to do something a little more complex when creating a product, do I have to manually write all the input args?

Anybody here use

graphql-shield

with

nexus@next

??

Anybody know how to get a count on a relation field in nexus-prisma? For example:

export const User = objectType({
  name: 'User',
  definition(t) {
    t.model.id();
    t.model.followers({
      type: 'OtherUser',  
    }).count;
  },
});

Has anyone successfully launch nexus on netlify?

I’m trying to simply use netlify in order to introspect my queries in a development environment.

I'm trying to do an upsert during a connect and it does not appear that this is a feature. Anybody done something like

create {
  field: {
    upsert {}
  }
}

Anybody know if you can

extendType

a model in nexus and then use

t.crud

to expose it?

Hey, quick question (cc @tgriesser)

https://github.com/graphql-nexus/schema/blob/develop/examples/ghost/src/data-sources/Context.ts < looking at the Ghost example, I wanted some clarification around how this pattern avoids memory leaks?  It appears that 

Context

 references the data sources, and that the datasources reference 

Context