src/generated/prisma.graphql

might be what you're looking for

that is what i’m looking for.. i’m migrating from a beta version, and for some reason, that schema file isn’t being generated even though I’ve specified a path in

prisma.yml

the easiest is to just generate a new project and copy stuff over

`Writing database schema to

schemas/prisma.graphql

234ms`, but no dice

at least that's what I did

hokay

I used token when accessing a prisma API, but it does not work. The code I used in front-end are:

code

    const httpLink2 = new HttpLink(
      {
        uri: '<https://us1.prisma.sh/public-motleyrat-429/prisma-node-adv/dev>',
        headers: {
          "Authorization": "Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VySWQiOiJjamNpNnZneDI1NHhwMDEyOHN6aGsxbDc4IiwiaWF0IjoxNTE2MTQ3NzI5fQ.zDkFMAuQHmguUKGioGBG26ehMYA80RdWW9E3Amf_Kz0"
        }

      },
    );

    const client2 = new ApolloClient({
      link: httpLink2,
      cache: new InMemoryCache(),
    })

    client2.query({ query: gql`{ posts { id
            title
        } }` }).then(() => {
      console.log('finished');
    });

I got this error: Uncaught (in promise) Error: Network error: Server response was missing for query 'null'.

is there an upgrade path to follow from a gcf project, or is that in the works?

@iamclaytonray and anyone else annoyed by the multitude of ‘dancing parrots’, Instructions to disable animations in Slack: https://www.google.com/search?q=slack+disable+animated+avatars&oq=slack+disable+animated+avatars&aqs=chrome..69i57.9764j0j1&sourceid=chrome&ie=UTF-8

@chaim pinned a message to this channel.

anyone else having issues deploying locally on Windows with Prisma? Schema seems to be messed up compared to when I'm running the "yarn dev" server

😞

I have bug to report: in resolver-forwarding example, in prisma.yml, on line 13, it is

datamodel: database/datamodel.graphql

but it should be

datamodel: datamodel.graphql

Are there any known issues on Graphcool Simple API at this time? I have Sentry.io error reports coming in that users are receiving occasional 504 Gateway Timeout errors

and then when this error is received, the response contains a non-JSON body. Triggering another error - "Unexpected token < in JSON at position 0"

Is there any way to forward every eligible requests to prisma from resolvers? I would like to front-end easily access the auto-generated APIs. Thanks.

Hi all! I start yarn dev and it`s OK. Can i run npm run build AND pm2 like pm2 start dist ?

I can not start playground via pm2

P.S. using prisma

i guess i can

pm2 start npm -- start npm-run-all --parallel start playground

I just tried out Prisma.. i am blown away. Great job 🙌

Any chance to get a Prisma + auth0 example?

Any ETA on Prisma Cloud?

Hey the docs mention the repository git clone https://github.com/graphcool/frontend-examples.git but it isn't there ...

So what is Graphcool now? like this is a name of the company that develop Prisma (framework?)? 🙂

Even this example seems to be broken - https://www.prismagraphql.com/docs/quickstart/fullstack/react/apollo-tijghei9go

It asks to do a 'prisma deploy' but I have only installed graphql-cli which doesn't have prisma.

Anyone else having issues accessing https://console.graph.cool/?

Is there a bit in the Prisma docs somewhere that explains where the DB connection is set / configured? Perhaps I missed it…

Like, can you have a Prisma server and point it at an AWS RDS instance?