Is there some sort of reference freeing magic going on under the hood here?

With my apollo-resolvers package, I had to implement some hacky magic to avoid this problem: https://github.com/boltsource/apollo-resolvers/blob/master/src/context.ts#L14

the context is created once per-request, and so it should just be gc’ed naturally as long as it’s not referenced by anything long-lived

So that makes sense, but it appears that Context is referenced by the data source class instances and vice versa creating a circular reference

I could be fundamentally misunderstanding something, but my rather dated understanding of V8 and ECMA standards leads me to believe that circular references aren't automatically GC'd

Since the reference count on both objects is still greater than zero

They should be as long as there’s nothing retaining the root context

I’ve been using the pattern for awhile with 50-100 data sources off of the root context and seen any issues w/ memory leaks for it. It’s basically attempting to simulate a thread local state for JS

Yeah totally, it's a pattern i've used for a while as well. I just wanted to understand what best practices look like for an API built with Prisma, and wanted to make sure that I am not misunderstanding something

https://github.com/graphql-nexus/schema/blob/develop/examples/ghost/src/data-sources/UserSource.ts#L10 < so like right here

there is def a circular reference, was wondering if

weakmap

or something like it is being used but perhaps my GC knowledge is a bit rusty at this point haha

One last question: is there a way to share context outside of GraphQL easily with the normal nexus context "autoload" pattern? E.g. share between GraphQL resolvers and regular old express handlers (for use in webhook handlers, SSO, etc)

So I am trying to deploy my application to heroku using docker, but I am getting key issues when it comes to transpiling nexus types… I have in my generate function

GENERATE_ARTIFACTS=true ts-node --transpile-only src/index

but it doesn’t close the connection. Is there a better way to transpile? I’m using apollo-server-express

Ok I finally got nexus working with Prisma2 and apollo on Heroku with docker. Do you guys think a tutorial would be helpful?

Can somebody please better explain to me the differences between the upcoming Nexus framework and the current Nexus Schema package. I see the message in my terminal but I’m not sure exactly which I need. For example, I’ve set up a fairly basic app using Prisma (2) and use nexus (how I did with Prisma 1) to expose certain CRUD operations. If that’s the extent of what I want to do, should I “continue using the Nexus Schema package please” by installing

@nexus/schema

or should I look into transitioning to the Nexus framework? I worry a little as I’ve had a few big refactors with Prisma over the past year with how things have changed and now I’m up-to-date with Prisma 2 (beta 3), I don’t want to settle on a nexus implementation I don’t fully understand and go live with something I’ll have to change down the line.

@nikolasburk Are you considering serverless as an option for Nexus framework? Or is serverless something you rather wouldn’t recommend for prisma or graphql apis in general?

For those struggling with the new

nexus@next

framework (not

@nexus/schema

) and

graphql-shield

, I’m working on a plugin, that’ll help you. Link coming soon…

I was struggling to figure out how to relate a particular nexus model. I have

User

and

Cart

Where it is a 1:1 relationship between the two. How do I do a query similar to

t.crud.cart()

if I want it to return the cart of the particular user? Do I have to create a custom resolver or does nexus provide a way to return cart of self within the arguments?

I thought it would make sense to do…

t.crud.cart({ WhereUserIdIsInique: User });

or something

ah nvm. I got it. It wasn’t working because I forgot to add Cart to types in MakeSchema. Also I can just use graphql Shield to do the authorization outside the querying logic of nexus.

Checkout my plugin to get basic jwt authentication working with

nexus

. Please let me know your thoughts and how I can improve it 😄 https://github.com/Camji55/nexus-plugin-jwt-auth

And there is

nexus-plugin-shield

a port of

graphql-shield

for nexus! Rules and shield configuration are fully compatible. https://github.com/lvauvillier/nexus-plugin-shield

Hi, did anyone run into

Property 'prisma' does not exist on type 'NexusContext'.ts(2339)

?

How do you handle errors? I want to add statusCode to a response. Something like this:

"errors": [{
  "message": "..."
  "statusCode": "..."
  "locations: "..."
}]

is it possible with nexus? any ideas are appreciated

Does anyone have a few minutes to help me with a roadblock in prisma-nexus? I'm setting up a test repo based on https://github.com/prisma/prisma-examples/tree/master/typescript/graphql-apollo-server, but trying to upgrade from

@nexus/schema

to

nexus

framework

I think I almost have it working, until

% yarn build
yarn run v1.21.1
$ nexus build
 877 ● nexus:build getting used plugins
 376 ● nexus:plugin:nexus-plugin-prisma Running Prisma generators ...
 411 ● nexus:build starting artifact generation
4020 ● nexus:build building typescript program
2822 ● nexus:build starting addToContext type extraction
   3 ● nexus:build Awaiting artifact generation & addToContext type extraction
   3 ● nexus:build Compiling a production build
Error: node_modules/@types/typegen-nexus/index.d.ts:11:7 - error TS2503: Cannot find namespace 'Prisma'.

11 'db': Prisma.PrismaClient
         ~~~~~~

    at Object.compile (/home/oliver/farmly/microservices/users/node_modules/nexus/dist/lib/tsc.js:63:15)
    at Object.buildNexusApp (/home/oliver/farmly/microservices/users/node_modules/nexus/dist/lib/build/build.js:63:11)
    at async Build.parse (/home/oliver/farmly/microservices/users/node_modules/nexus/dist/cli/commands/build.js:31:9)
error Command failed with exit code 1.

My current code can be found here: https://github.com/OliverEvans96/graphql-nexus-prisma-test

Is it possible to generate the resulting graphql schema from nexus framework without the server running?

Hello, I am trying to add a field that counts all of the entities of my database. I added the following field declaration in the query type:

t.field('count', {
      type: 'CountPayload'
});

And then I declared my count payload type as this:

const CountPayload = objectType({
  name: 'CountPayload',
  definition(t) {
    t.field('patient', {
      args: {
        where: arg({ type: 'PatientWhereInput' })
      },
      type: 'ModelCount',
      resolve: async (parent, args, ctx: Context) => {
        const { prisma } = ctx;

        return {
          count: await prisma.patient.count({ where: args.where })
        };
      }
    });
  }
});

const ModelCount = objectType({
  name: 'ModelCount',
  definition(t) {
    <http://t.int|t.int>('count');
  }
});

However this is not working ☹️. The

count

field in

queryType

is returning null. I want the resolve to come from the subfield. Is there a way to achieve this?

I want the query field to execute the resolvers in the subfields, basically