Never mind, I figured it out

Can you see the console functions ?

Can someone help me out with this issue. Here is the link to the issue i posted on the forums. https://www.prisma.io/forum/t/cant-pass-info-into-mutation/3961

has anyone used AWS Cognito with Prisma?

Got a weird issue. Querying all users works fine, but when querying a single user by id it returns null - even though the id is correct.

query {
  users {
    id
    email
  }
}

gives:

{
  "data": {
    "users": [
      {
        "id": "63f14583-de97-429a-bfc0-c296eb636e6d",
        "email": "<mailto:christian@jenkins.no|christian@jenkins.no>"
      }
    ]
  }
}

but this:

query {
  user(where: {
    id: "63f14583-de97-429a-bfc0-c296eb636e6d"
  }) {
    id
    email
  }
}

gives:

{
  "data": {
    "user": null
  }
}

Querying by only email works. Id and email are unique.

Hello guys, I am new to GraphQL and I wanted to know if someone could answer a question for me. I am passing a public token that is being exchanged for a private token that comes with meta data, which we can call token_items. I wanted to create this token_item and update a user at the same time. Does anyone have a good way of doing this? So my Graphql schema is

User {
  id: ID! @unique
  name: String!
  token_items: [Token!]!
}
Token {
  id: ID! @unique
  info: String!
  carrier: String!
}

I've tried something along the lines of:

mutation {
  updateUser (
    where: {
      id: "1234"
    },
    data: {
      create: {
        info: "1234"
        carrier: "1234"
      }
   }
  )
  {
    id
    name
    email
    token_items {
      id
      info
      carrier
    }
  }
}

Hey all. I'm having an issue running

yarn prisma deploy

with the following error:

Error: Whoops. Looks like an internal server error. Search your server logs for request ID: local:management:cjjhlsbf4000n0910xoq3oage: {"response":{"data":{"addProject":null},"errors":[{"message":"Whoops. Looks like an internal server error. Search your server logs for request ID: local:management:cjjhlsbf4000n0910xoq3oage","path":["addProject"],"locations":[{"line":2,"column":9}],"requestId":"local:management:cjjhlsbf4000n0910xoq3oage"}],"status":200},"request":{"query":"      mutation addProject($name: String! $stage: String! $secrets: [String!]) {\n        addProject(input: {\n          name: $name,\n          stage: $stage\n          secrets: $secrets\n        }) {\n          project {\n            name\n          }\n     }\n      }\n      ","variables":{"name":"default","stage":"default","secrets":null}}}

So I was able to solve it. What I did was I just created the token_item and connected it to the user like so:

mutation {
  createTokenItems (
    data: {
      info: "foo"
      carrier: "bar"
      connect: {
        id: userId
      }   
    }
  )
}

i also changed my schema to this:

User {
  id: ID! @unique
  name: String!
  token_items: [Token!]!
}
Token {
  id: ID! @unique
  info: String!
  carrier: String!
  owner: User
}

hey guys! glad to join this slack channel.... So i have deployed a graphql server and prisma container onto AWS, and now i have started coding some examples from howtographql... everything went smooth except that i cant do anything in the app playground... dev playground is fine... but whenever i try to query or mutation in the app playground, i would get token is invalid... i m using the authorization header token for both the dev and the app....

@Timo Have you followed the tutorial from here?

It stores your token currently in local storage

const httpLink = new HttpLink({ uri: '<http://localhost:4000>' })

const middlewareAuthLink = new ApolloLink((operation, forward) => {
  const token = localStorage.getItem(AUTH_TOKEN);
  const authorizationHeader = token ? `Bearer ${token}` : null;
  operation.setContext({
    headers: {
      authorization: authorizationHeader
    }
  })
  return forward(operation)
})

or in the server:

function getUserId(context) {
  const Authorization = context.request.get('Authorization')
  if (Authorization) {
    const token = Authorization.replace('Bearer ', '')
    const { userId } = jwt.verify(token, APP_SECRET)
    return userId
  }

  throw new Error('Not authenticated')
}

It should be in this tutorial for the serverside if using node: https://www.howtographql.com/graphql-js/0-introduction/

The TypeScript generator is generating all kinds of errors

Is it possible to use Prisma Cloud when your Prisma server is hosted on a Fargate instance? I'm getting a "cannot connect to server" error

Has anyone had any success deploying Prisma with Kompose? http://kompose.io

If many users are going to be requesting the same query, does Prisma do any caching? Or should this be handled by my node server instead?

Hmm, I just tried adding a new Prisma server with Heroku and went through this flow:

I got the success message and can also see the new dyno up on Heroku. However I can’t see the server on Prisma Cloud, and the last green button in the image above just takes me back to the start (i.e. adding a new service)

I guess I’m missing something obvious?

Can’t really find any details in the docs either so I’m not sure if there’s another step involved here

Hi all

Is Graphcool Cloud console down for anyone else?

It is down for me

https://status.graph.cool/ offers no useful information

When I visit https://console.graph.cool/ I see an eternally displayed loading indicator and there are errors in the console.

Our app, built on Graphcool, is also down now as a result