Models newly defined in schema.prisma are not strongly typed in my resolver until I restart VS Code. What am I missing?

[uncvrd]

Hi! I have the following workflow, but for some reason I cant access my Album model in my ctx until I restart VS Code. What am I doing wrong? (This is all while nexus dev is running)

First I define my Album object in api/graphql/album:

schema.objectType({
    name: 'Album',
    definition(t) {
        t.int('id')
        t.string('title')
        t.string('uid')
        t.int('appleId')
        t.date('date')
        t.string('imageURL')
    }
})

I then define the model in schema.prisma

model Album {
  id Int @id @default(autoincrement())
  title String
  uid String @unique
  appleId Int @unique
  date DateTime
  imageURL String
}

I save, and now my CLI prompts me to run the two save and up commands. I open another terminal window within the project directory, and run those commands. I type Y to restart the server now that the migration is complete.

Now, I head back over to api/graphql/album and start to define a Query making use of collocation. However, my album is not defined in my resolver ctx.db.album.findOne().

schema.extendType({
    type: 'Query',
    definition(t) {
        t.field('album', {
            type: 'Album',
            args: {
                id: schema.intArg({ required: true })
            },
            resolve(_root, args, ctx, info) {
                return ctx.db.album.findOne({
                    where: {
                        id: args.id
                    }
                })
            }
        })
    }
})

The only way I've gotten around this is to just close out of VS Code completely and then reopen. When I do that, album is available on my ctx.db object.

What am I missing in my workflow to get this strongly typed typescript support after i run the migration? Thanks!

Edit: here are my dependencies:

  "dependencies": {
    "nexus": "^0.25.0",
    "nexus-plugin-prisma": "^0.16.1"
  },

[steinathan]

Mine works just fine, trying running the prisma generate command and see if that will fix it 😊

$ npx prisma generate

Sometimes VSCode fails to update the current types on time

[uncvrd]

@navicstein hmm I just tried running npx prisma generate after migrations and restarting the server and it still didn't work for me unfortunately :(

Checking the index.d.ts, I see the above message as an error. My Artist types are defined lower in that file, I don't know why VS Code is having issues with this.

Edit:

NOW that I opened that index.d.ts I can access the artist object on my context, I'm so confused! Not sure what's going on here.

[Weakky]

Erf. That's unfortunately a VS Code problem. We've worked hard to prevent that from happening but it looks like there are still cases where this happens.

The TLDR is that, as we regenerate the typings, VS Code doesn't always pick up these changes and so the types end up not being refreshed and you don't see these new typings. Most of the time, when that happens, you have two options:

• Restarting the TS Server
  

• CMD + CTRL clicking on either the Prisma Client or a Nexus method so that it brings you to the typings, which should make VS Code refresh those typings. Just like you ended up doing.

While this is not ideal at all, we're still actively looking to understand why VS Code is properly picking these changes for some people and why it's not for others. If you're interested in helping us solve this problem, we'd love to know more about your OS and even maybe a small reproduction on your side. Feel free to create a proper issue to discuss that so that other people can chime in if they ever encounter that same problem.

Marking it as answered for now 🙌