Currently I am doing something like this

function createCategory(parent, { input }, ctx, info) {
    const category = ctx.db.mutation.createCategory({ data: input });

    return {
        edge { node: category }
    }
}

If I am passing

info

to

ctx.db.mutation.createCategory

I am getting error about subselection

Hi, what is the best practice to keep track of ordering/positioning/ranking in relations? Example:

type List @model {
  id: ID! @isUnique
  name: String!
  tasks: [Task!]! @relation(name: "ListOnTask")
}

type Task @model {
  id: ID! @isUnique
  list: [List!]! @relation(name: "ListOnTask")
  name: String!
}

Given I can have one task in multiple lists how can I define order/position/rank of the task within each list separately?

Is graph.cool deprecated? Should I be using prisma?

Also something's wrong with the docs

ugh now the site is down

nvm it's just laggy

@nilan Is there a way to remove unwanted resolvers (or define them completely myself), without leaving the graph.cool ecosystem (graph.cool, prisma)? What I basically want, is to remove all but one of the default query resolvers for security reasons and hock up a database to store the data and make it accessible to other systems. Thanks in advance! 👍

Is the graphcool cloud service still supported?

Sounds like no

docs are messed up, the navigation menu changes the url but not the contents

Hi all, I have migrated from the graph.cool service to Prisma, everything went well and i have deployed the Types and Enums into my development cluster. How can i export all the data from graph.cool (for each type) and import it into the new schema?

Just to make sure I understand it correctly. Graphcool runs mysql as database by default?

Hello there, noob question incoming... I'm new to prisma and just tried to create a mutation resolver. I added it to schema.graphql:

type Mutation {
  createDraft(title: String!, text: String): Post
  deletePost(id: ID!): Post
  publish(id: ID!): Post
  createSite(urlhash: String!): Site
}

and to index.js:

Mutation: {
    createSite(parent, { urlhash }, ctx, info) {
      return ctx.db.mutation.createSite(
        {
          data: {
            urlhash
          },
        },
        info,
      )
    },
  },

But I still get the error "Unknown argument 'urlhash' on field 'createSite'", if I call the mutation like this:

mutation{
  createSite(urlhash: "dqwda")
  {id}
}

What am I doing wrong?

Okay, am I correct with the assumption, that I can only access the created mutations from the localhost:4000 and not the playground?

you should be able to access them in your local playground

Well I don't, but funny enough, I can access them, when I connect my application to localhost:4000.

it runs at http://localhost:4466/server/dev by default

Guys try to stick to threads pls 💚

How can I access the local mysql db running on docker with heidisql or any other mysql editor/viewer?

I'm using the node advanced boilerplate with authentication. I just upgraded prisma and now when I have an Authorization header set to a user in the graphql playground it tells me that

no Node for the model User with value ...

except when I query me I get back the correct token

any ideas on what could be causing this?

hey everyone 🙂

has anyone here deployed their backend to aws using the fargate blog tutorial recently? 🙂 https://blog.graph.cool/how-to-deploy-a-prisma-cluster-to-aws-fargate-using-docker-cloudformation-293aa8727b89

i'm having an issue deploying the fargate template 😞

"Unable to assume the service linked role. Please verify that the ECS service linked role exists."

Hello, I would like to create

Advice

and connect to it, already created, tags, categories, videos and images. Yet for some reason this this setup does not work - i don't know how to set tags, categories, videos and images inputs so that it does not throw error.

type Mutation {
  createAdvice(params: CreateAdviceParams!): Advice
}

type Advice {
  id: ID!
  name:String!
  value: Int!
  description: String!
  tags: [AdviceTag]!
  categories: [AdviceCategory]!
  videos: [VideoAsset!]!
  images: [ImageAsset!]!
}

input CreateAdviceParams {
  name:String!
  value: Int!
  description: String!
  tags: [AdviceTag]
  categories: [AdviceCategory]
  videos: [VideoAsset]
  images: [ImageAsset]
}

Mutation: {
        createAdvice(parent, {params}, ctx, info) {
            return ctx.db.mutation.createAdvice({data: params}, info)
        },
    },

mutation {
  createAdvice(params:{
    name: "Saraasdh"
    value: 1,
    description: "Jakis tam description",
    tags: { connect: [{
      id : "cjfr8wmere6bt0a422693ql94"
    }]},
    categories: { connect: []},
    videos: { connect: []},
    images: { connect: []}
  }) {
    id,
    name
  }
}

hi @nilan @sorenbs any ideas about the error with fargate blog tutorial 😄

Could someone show me an example, how a resolver for a deletion of a node and it's (via id) related children should look like?

Prisma should generate Mutations by itself? Is it possible? Im tired of trying to define proper mutations with nested mutations... There is no examples that are advanced (like "create Object and connect to it other already created objects of different type") 😕