Hey guys, anyone with an idea on how i can query for an authenticated user using his/her token? using graphql-yoga, and prisma API. Please explain how i can i go about it or just provide a link to a good resource where i can find the info @Harshit

if

componentA

loads a query like this:

<Query query={EVENT_QUERY} variables={{ slug: this.props.match.params.slug }}>

with the following qgl:

export const EVENT_QUERY = gql`
  query EventQuery($slug: String!) {
    event(slug: $slug) {
      id
      slug
      description
      title
      dates {
        id
        timestamp
      }
      places {
        id
        name
        url
      }
      participants {
        id
        name
      }
      menus
    }
  }
`;

And then I pass

participants

to

componentB

What if

componentC

makes a

create mutation

and adds a new

participant

to that event... How should I update the original query so that the changes with cascade down to components A and B?

Does anyone know how to get the graphql-boilerplates running? There are no folder created after installation. There are a bunch of issues regarding this but no solutions 🤔 https://github.com/graphql-boilerplates/node-graphql-server/issues/449 https://github.com/graphql-boilerplates/react-fullstack-graphql/issues/562 https://github.com/graphql-boilerplates/node-graphql-server/issues/302

Another question for people using prisma in production, if I have a hosted database connection (so not on the same droplet as my prisma server), how scalable does the prisma endpoint itself need to be? It is a sort of proxy to and from my db but I am not sure how much power this would need

Hello everyone, I have a settings page where the user can update their email, first name, and last name. I am getting the following error when I submit the data from the settings page:

[GraphQL error]: Message: You provided an invalid argument for the where selector on User., Location: , Path: updateUser

Uncaught (in promise) Error: GraphQL error: You provided an invalid argument for the where selector on User.

schema.graphql

...
# import * from './generated/prisma-client/prisma.graphql'

updateUser(email: String, firstName: String, lastName: String, password: String): User!
...

Mutation.js

async updateUser(parent, args, ctx, info) {
    // First check if there is a user with that email
    const user = await ctx.db.query.user({ where: { email: args.email } });
    if (user) {
      throw new Error(`The email ${args.email} is already being used`);
    }
    const updatedUser = await ctx.db.mutation.updateUser({
      where: { id: args.id },
      data: {
        email: args.email,
        firstName: args.firstName,
        lastName: args.lastName
      }
    });
    return updatedUser;
  }

Frontend Mutation:

const UPDATE_USER_MUTATION = gql`
  mutation UPDATE_USER_MUTATION(
    $email: String!
    $firstName: String!
    $lastName: String!
  ) {
    updateUser(email: $email, firstName: $firstName, lastName: $lastName) {
      id
      email
      firstName
      lastName
    }
  }
`;

What am I doing wrong here?

If anyone here was succesful in connecting a Prisma server to digital ocean hosted db, please let me know!

I keep getting errors

hey folks ! Any idea when we’ll be able to have multiple field unique constraint ?

ha it seems it’s planned for february 🙂 https://github.com/prisma/prisma/issues/3405#issuecomment-456323909

Is there roadmap page for this project? Client and Cloud?

Is there any way to expose an enum as argument in a query or mutation with nexus?

i need help regarding querying nested objects with prisma on mongo

i'm building a graphql based api

using typescript and mongodb

I need some help with prisma init. I'm trying to connect an empty MySQL-DB on localhost and am getting a TypeError. Can anybody offer some advice?

Hey guys; what do you guys recommend for storing date of births in the DB?

Storing it as DateTime ?

or as a string

nevermind, realized DateTime could be converted by ISO

Hi, I’m interested to know if anyone has some good examples of resolver unit tests, preferably in typescript? The most challenging piece would seem to be mocking

prisma

on

context

. It might simply come down to needing to

@ts-ignore

every use of a mock prisma seeing as the type definition is pretty huge to replicate an instance of. Thanks!

Hello guys! I think this tutorial:

<https://www.prisma.io/tutorials/bootstrap-a-graphql-server-in-typescript-ct09/>

is outdated. This tutorial was supposed to use prisma-binding but instead, it uses prisma-client. Thanks.

Hi. I am trying to mutate a nested array as described in this question: https://www.prisma.io/forum/t/mutation-creating-nested-mutation-with-array-and-objects/4766

Where I am lost is, how do I reference this kind of type:

LineItemCreateManyWithoutInvoiceInput

Since it’s not anywhere in my custom

schema.graphql

hi guys

did anyone have any problems querying parent entity and getting nested entities

?

Does anyone knows if it's planned to integrate nexus fully with prisma? I mean, when you deploy prisma, overwrite prisma's client with nexus, and we would don't need a index.ts file. If you are using nexus doesn't make sense deploy the prisma server because it's reading from its own client not the new one created with nexus.

Hi. I just use nexus-prisma, it works well except I don't see schema.graphql in

generated

folder. There is no errors when running graphql server, does anyone have this problem and how to fix it. Thanks!

const Query = prismaObjectType({
    name: 'Query',
    definition: t => t.prismaFields(['*']),
  })
  const Mutation = prismaObjectType({
    name: 'Mutation',
    definition: t => t.prismaFields(['*']),
  })

  const schema = makePrismaSchema({
    types: [Query, Mutation],
    prisma: {
      datamodelInfo: metaSchema,
      client: prisma,
    },

    outputs: {
      schema: path.join(__dirname, './generated/schema.graphql'),
      typegen: path.join(__dirname, './generated/nexus.ts'),
    },
  })