SOLVED Hi everyone I just located an issue with the typescr Prisma #prisma-whats-new

(SOLVED) Hi everyone, I just located an issue with...

Moritz

02/02/2018, 12:27 PM

(SOLVED) Hi everyone, I just located an issue with the typescript boilerplate: In the typescript boilerplate there is a file

src/generated/prisma.ts

with the header text:

Copy code

# THIS FILE HAS BEEN AUTO-GENERATED BY "PRISMA DEPLOY"
# DO NOT EDIT THIS FILE DIRECTLY

However, when I delete the file and redeploy, it does not get regenerated and

yarn dev

gives an error complaining that it is not there. This is a problem, since any auto generated files should be regenerated and not statically expected. I ran into this issue when migrating an existing node-prisma app to typescript. Any help?

Moritz

02/02/2018, 12:34 PM

Mhhh, nevermind, it does get regenerated in the typescript boilerplate, sorry for the overreaction 🙂 what part of the config is needed to generate this file? Ill try to dig deeper myself!

Moritz

02/02/2018, 12:37 PM

found it in `.graphqlconfig.yml`:

Copy code

prepare-binding:
        output: src/generated/prisma.ts
        generator: prisma-ts

plase excuse my stupid interruption 🤒

nilan

02/02/2018, 12:42 PM

hey @Moritz that part has been confusing to others already 🙂 I wonder how we can better cover it in our documentation.

prisma deploy

has a hook for

graphql prepare

, which checks the

prepare-binding

information in

.graphqlconfig.yml

Moritz

02/02/2018, 1:03 PM

@nilan thank you, that makes sense. I just overlooked the

graphqlconfig.yml

2 Views

Open in Slack

Previous Next