I tried making a reset password with Prisma using JWT tokens and email. I'm fairly new at node server development and graphql in general. I would appreciate if someone could look it over and give me some critique: https://gist.github.com/ameistad/046b7bbdc6f69631d7d7347cb72594da

Is it possible to return the aggregate > count in graphcool framework? I'm trying to do:

query allPostsCommentsQuery {
    allPostses (orderBy: createdAt_ASC) {
      aggregate {
        count
      }
      __typename
      id
      displaysrc
      caption
      likes
      comments (orderBy: createdAt_DESC) {
        __typename
        id
        posts {
          __typename
          id
        }
        text
        user
        deleted
      }
    }
  }

Hi, I am working on the tutorial 'Building a GraphQL server with `graphql-yoga`' with Prisma 1.7 and trying to invoke a post-deployment hook to generate the schema. I have included the following line in prisma.yml: "- graphql get-schema --project blogr" - I get an error when going for prisma deploy: " 'ENOENT': spawn graphql ENOENT" . Any idea why this is? Many thanks

is there a way to add comments or notes in

schema.graphql

? For example, here I want to say that I need the

ids

of the images.

Is it just me, or did the login link get removed from the website? I only have the option to signup, and now I can reach my account 🤔

I’m working with template Graphcool/templates/Auth/email-password

Hi! I'm having trouble with the below upsert mutation. Oddly, it goes through without an error, but none of the relations get established. Can anyone lend a set of fresh eyes and check if I'm doing something dumb?

A file was commented on

A file was commented on

A file was commented on

A file was commented on

A file was commented on

A file was commented on

Hi everyone! Does anyone know if the graphql-yoga lambda function supports any sort of formatErrors object? I've been getting

unexpected token I in JSON at position 0

kind of error so I know my errors aren't being thrown right.

Any ideas how to solve this error?

ERROR: Whoops. Looks like an internal server error. Please contact us from the Console (<https://console.graph.cool>) or via email (support@graph.cool) and include your Request ID: XXXXXXXXXXXXXXXXXXXX

{
  "data": {
    "push": null
  },
  "errors": [
    {
      "message": "Whoops. Looks like an internal server error. Please contact us from the Console (<https://console.graph.cool>) or via email (support@graph.cool) and include your Request ID: XXXXXXXXXXXXXXXXXXXX",
      "requestId": "XXXXXXXXXXXXXXXXXXXX",
      "path": [
        "push"
      ],
      "locations": [
        {
          "line": 2,
          "column": 9
        }
      ]
    }
  ],
  "status": 200
}

I tried pushing to one of my services but it is producing this error.

Hej - I’m trying to setup a middleware logger to log each incoming query to the graphql server. It’s giving a log entry per each resolver. Is there a way to only log based on the original top level query?

const logMiddleware: any = async (
  resolve: any,
  parent: any,
  args: any,
  ctx: any,
  info: any): Promise<any> => {
  <http://logger.info|logger.info>(info);
  return resolve();
};

export const server: GraphQLServer = new GraphQLServer({
  schema: schema,
  middlewares: [logMiddleware]
});

@nilan are there any updates on the issues related to deploying? (i.e. https://github.com/graphcool/graphcool-framework/issues/517) the workaround mentioned in the github issue doesn't work for us at all

Does the local playground do some kind of caching? I dont see my newly added mutations and keep seeing mutations of stuff I long deleted. I tried restarting the the server several times but to no avail

Hello folks, anyone has issues with

graphql prepare

not regenerating (or modifying to add field) the

prisma.graphql

file properly after

prisma deploy

?

I do have

hooks:
  post-deploy:
    - graphql get-schema --project prisma
    - graphql prepare

in my

prisma.yml

file

I guys someone can help me for this error

$ prisma deploy
Deploying service `s-cool` to stage `dev` to server `prisma-eu1` !

ERROR: The provided name: coursesByDriver is not a valid name for a relation. It can only have up to 54 characters and must have the shape [A-Z][a-zA-Z0-9]*

{
  "data": {
    "deploy": null
  },
  "errors": [
    {
      "locations": [
        {
          "line": 2,
          "column": 9
        }
      ],
      "path": [
        "deploy"
      ],
      "code": 4004,
      "message": "The provided name: coursesByDriver is not a valid name for a relation. It can only have up to 54 characters and must have the shape [A-Z][a-zA-Z0-9]*",
      "requestId": "eu1:cluster:cjgnhh5ufpnuy0b18lwcu1nvf"
    }
  ],
  "status": 200
}

Get in touch if you need help: <https://www.graph.cool/forum>
To get more detailed output, run $ export DEBUG="*"

Any advise how you would page a search in prisma? for example I'm searching by user and I want to return 50 results at a time to the client.

Would this work?

How can I use machine learning together with graph cool?

will graphcool eventually become prisma ...i am not a fan of Typescript????

maybe this is a rather simple question but when I want to create a Product and nested price data in the form of Currency types, how do I provide my server with the Currency data? Those are objects and Im having difficulty adding those as input variables to my mutation.

Hohai, there used to be a

_typeMeta

field available on GCF, which was replaced by

aggregate

now on Prisma. The thing is, when you had a one-to-many relationship, that

_typeMeta

was available inside the “many” relationship, allowing to query how many items were linked to that type. As instance, let’s say I have a

Brand

type and a

Product

type, linked by a one-to-many. We used to be able to query something like

allBrands { id _productsMeta }

, allowing for instance, to prevent from deleting a

Brand

that had `Product`s linked to it

if _productsMeta > 0

. How are we supposed to do the same with Prisma ?

Hey guys ! Someone use prisma with vue.js + apollo ?

@channel - I would like to get info on MongoDB and elastic search connectors.