Prisma

this is a guess, but what does your prisma.yml say?

sorry, not prisma.yml. i meant .graphqlconfig.yml, the projects section specifically

in that case, sorry, i won’t be of much help.

Hey! Frontend dev just starting out using prisma and GraphQL-yoga to build a backend. I have two questions I have been trying to get answers to and haven’t had any luck. 

1. How do I write unit tests to test my API
2. Do i have to deploy both prisma service and graphql-yoga server or is there an all in one solution?

<@UAVF0TSJK>
1. check out this forum post: <http://www.prisma.io/forum/t/test-graphcool-framework-resolvers/2172/5>
2. You have to deploy both prisma and a graphql-yoga server. You can pay Prisma to host your service or you can run it in docker. I use Apex Up to host my graphql-yoga server but you could use docker.

is there any way to pull an existing graphcool setup from the web console into a local project via the cli so that i can then add templates or edit files and deploy back up to graphcool in the cloud?

```"data": null,
  "errors": [
    {
      "message": "Whoops. Looks like an internal server error.```

seems like I have a connection. but for some reason, my playground is down.

ok, good to know im not the only one. What is it? Like an update they're doing to Prisma? Like a process that just runs once a day?

Seems like the prisma dev cluster is erroring

this has been resolved :slightly_smiling_face:

the demo servers are up again :slightly_smiling_face:

We love you <@U0RQY0KK5> ! What happened?

We logged connection problems in specific services on the demo server :slightly_smiling_face:

I’m getting the same error here, I thought it was something on my end

it's resolved now :slightly_smiling_face:

I keep getting 
```
ERROR: Whoops. Looks like an internal server error. Search your server logs for request ID: us1:management:cjhihwnalawzk0b62ca7umdyp

{
  "data": {
    "addProject": null
  },
  "errors": [
    {
      "message": "Whoops. Looks like an internal server error. Search your server logs for request ID: us1:management:cjhihwnalawzk0b62ca7umdyp",
      "path": [
        "addProject"
      ],
      "locations": [
        {
          "line": 2,
          "column": 9
        }
      ],
      "requestId": "us1:management:cjhihwnalawzk0b62ca7umdyp"
    }
  ],
  "status": 200
}
```

that's resolved now :slightly_smiling_face:

does anyone switch between using docker locally and prisma cloud?

can you switch between local docker and prisma cloud easily?

Im pretty new to this but I belive so. Do you have an .env file with your PRISMA_ENDPOINT?

<https://www.prisma.io/forum/t/migrating-data-from-docker-mysql-to-prisma-cloud/3016/2?u=nilan>

did anyone fix the `TypeError: Cannot convert undefined or null to object` after upgrading to `prisma@1.8.3` and `prisma-binding@2.0.1`?

did you checked <https://github.com/prismagraphql/prisma-binding/issues/162> ? there was breaking change in prisma-binding@2.0.0 how you should regenerate types

so you think if I update the `yml`files accordingly, and using `graphql codegen` it should fix this?

I was trying that, but `graphql codegen` did nothing, even though I got the message `Code for project database generated to src/generated/prisma.ts`

gave up and went back to `prisma@1.7.4` and `prisma-binding@1.5.19`

anybody using windows? It seems that `prisma deploy` (with latest version of prisma) in the latest boilerplate doesn't actually wind up generating anything (even though I can see it runs the hooks)

same thing for me, running windows... I need to run the hooks manually

can you provide a bug report on Github please? :slightly_smiling_face:

a related issue exists here: <https://github.com/prismagraphql/prisma-binding/issues/164>

<@U8ZQADW1H> you can try playing around with the `yml` files, I was not successful though

There's a lot of things happening in that issue, so it's difficult to keep track :slightly_smiling_face: but if you think your problem is covered there that's good!

I'm having issues deploying changes to Graph.cool framework - is something down this morning?
```
$ yarn deploy
yarn run v1.5.1
warning package.json: No license field
$ node -r dotenv/config $(which graphcool) deploy
✨  Done in 3.90s.
```

Ah, just run with `DEBUG=*` and it's now showing the error

Might be useful to show that though

```
 ▸    bad indentation of a sequence entry at line 247, column 5:
 ▸    - operation: Feature.read
 ▸    ^
```

that entry is not correctly indented :slightly_smiling_face:

Yep - I fixed it once I saw that error :slightly_smiling_face:. It normally tells me without debug mode that there's  an error, which it didn't this time.

Anyway, thanks for the help. Super :fire: support!!

just out of interest, does anyone use `graphql-request` instead of `apollo-client` on React? <https://github.com/prismagraphql/graphql-request>

Im using Prisma 1.7 as that’s what came with the React boilerplate. Should I update to  1.8?  <https://github.com/graphql-boilerplates/react-fullstack-graphql/blob/master/advanced/server/package.json>

if you do, you can refer to this upgrade guide: <https://www.prisma.io/docs/reference/upgrade-guides/upgrading-prisma/upgrade-to-1.8-aiqu3eicae>

<@U8N20JVC3> if you are using a windows machine be advised that you might run into problems running `graphql codegen`on 1.8 <https://github.com/prismagraphql/prisma-binding/issues/164>