So when I pass the {value: 2, text: "some text"} in as a variable I get the following error

: GraphQL error: Argument 'filter' expected type 'MemberFilter' but got: {occupation: $labour}. Reason: 'occupation' Field 'occupation' is not defined in the input type 'MemberFilter'.

Any ideas?

JSON.stringify(...) also does not work

query getWorkforce ( $labour: Json! ){ labour: _allMembersMeta(filter: {occupation: $labour}) { ... } }

const Workforce = graphql(GET_WORKFORCE_DATA, { name: 'getWorkforceData', options: { variables: { labour: {value: 2, text: "Labour"} } } })(workforce)

we keep getting this in our ECS logs when I try to do `prisma deploy`: "Warning: Management API authentication is disabled. To protect your management server you should provide one (not both) of the environment variables ". we definitely have

MANAGEMENT_API_SECRET

in the env. what would cause this?

Is there a recommended approach to sharing environment variables between

prisma.yml

(i.e. with

.env.prod

,

.env.dev

, etc) and the

index.js

file?

in this sort of setup: https://www.prisma.io/docs/tutorials/deploy-prisma-servers/aws-fargate-joofei3ahd#3.-deploy-a-prisma-service-to-the-new-server

hmmm. Makefile to the rescue, I think.

Hello Everyone, Will prisma 1.9 support introspection queries for mysql databases ?

hey everyone, kind of chasing my tail right now, and I was wondering if someone could lend a hand. I have basically built out my Apollo/React frontend and want to hook it into prisma/gql server/db. I've tried several different versions of the tutorials: https://www.prisma.io/docs/tutorials/setup-prisma/create-new-db/postgres-eiyov7erah/ https://www.prisma.io/docs/tutorials/build-graphql-servers/development/build-a-graphql-server-with-prisma-ohdaiyoo6c/ Which is fine and dandy, but I don't know if it gets me any closer to my goal. After doing those 2, I found this one about specifically setting up a frontend: https://www.prisma.io/docs/tutorials/connect-to-prisma-from-the-frontend-fbgaeyrou7 But it seems like some assumptions are made about what needs to happen first. More specifically, "The tutorial assumes that you already have a running Prisma service, so please make sure to have the endpoint of it available. If you're unsure about how you can get started with your own Prisma service, check one of these tutorials: Setup Prisma on a Demo server Setup Prisma with a new MySQL Database Setup Prisma with a new Postgres Database Setup Prisma by connecting your empty MySQL Database Setup Prisma by connecting your empty Postgres Database"

Again, I've done a few of these, but at this point, it seems like if I just setup a basic prisma init and do a deploy to create a service, I can just connect to it from the client. That being said, not sure how it would actually persist and save to a DB?

At this point Im not concerned with deployment, just trying to get something working

Has anyone else had Prisma cloud services stuck deploying / deleting? I have had this for a few days now.

For those who are interfacing with their Prisma backend through a web app with Vue or React — how are you deploying it? Especially if you’re on AWS, it seems like the options are S3 and ElasticBeanstalk and I’m curious about the differences.

Hey, is it possible to generate the schema.graphql in a way where we don't have to write every possible Query one by one ?

hmm in the current prisma cli 1.8 … ist it just me or are the boilerplates gone 😄?

Yeah they’re gone

Is there a practical limit on how many can be connected to Graphcool (SaaS) simultaneously, or queries per second?

I'm having issues with permissions, and now I'm getting an internal server error eu-west-1systemcjhke6dye1vuf0170a6r12irv

Is there a way of implemting custom directives ?

So I’m trying to use the TS advanced template (https://github.com/graphql-boilerplates/typescript-graphql-server/tree/master/advanced), but I’m getting a TS warning from the get-go that I don’t know how to resolve:

src/index.ts(5,34): error TS2345: Argument of type '{ typeDefs: string; resolvers: typeof "/.../src/...' is not assignable to parameter of type 'Props'.
  Types of property 'resolvers' are incompatible.
    Type 'typeof "/.../src/resolvers/index"' is not assignable to type 'IResolvers | undefined'.
      Type 'typeof "/.../src/resolvers/index"' is not assignable to type 'IResolvers'.
        Property 'default' is incompatible with index signature.
          Type '{ Query: { feed(parent: any, args: any, ctx: Context, info: any): Promise<Post[]>; drafts(parent:...' is not assignable to type 'GraphQLScalarType | (() => any) | IResolverObject'.
            Type '{ Query: { feed(parent: any, args: any, ctx: Context, info: any): Promise<Post[]>; drafts(parent:...' is not assignable to type 'IResolverObject'.
              Property 'Query' is incompatible with index signature.
                Type '{ feed(parent: any, args: any, ctx: Context, info: any): Promise<Post[]>; drafts(parent: any, arg...' is not assignable to type 'GraphQLFieldResolver<any, any, { [argName: string]: any; }> | IResolverOptions'.
                  Type '{ feed(parent: any, args: any, ctx: Context, info: any): Promise<Post[]>; drafts(parent: any, arg...' has no properties in common with type 'IResolverOptions'.

Can anyone tell me how fix that?

How do I use a SQL Client to connect to the MySQL docker container running locally on my development machine? I’ve tried

localhost:3306

to no avail, so I assume that the container may not be exposing any ports to connect too?

I'm using

prisma-bindings

, and finding that if I add keys on my subfields, sometimes the result will be shown as null, even though nodes exist. Does anyone know why that would be? Here's an example:

query {
  currentUser {
    organisation {
      usersWithInvite: users(
        where: { invite: { id_not: null } }
      ) {
        id
      }
    }
  }
}

returns:

{
  "data": {
    "currentUser": {
      "organisation": {
        "usersWithInvite": null
      }
    }
  }
}

If I add another

users

subselection, the whole query works as expected:

query {
  currentUser {
    organisation {
      users {
        id
      }
      usersWithInvite: users(
        where: { invite: { id_not: null } }
      ) {
        id
      }
    }
  }
}

returns:

{
  "data": {
    "currentUser": {
      "organisation": {
        "users": [
          ...manyUsers
        ],
        "usersWithInvite": [
            ...manyUsers
        ]
      }
    }
  }
}

hi friends how i can make this drawer slip i am using react js component

anyone seen this error before in prisma 1.8

Client does not support authentication protocol requested by server. Consider upgrading MariaDB client. plugin was = caching_sha2_password

Please consider using the Forum instead to discuss questions involving code snippets.

getting an error when trying to log into the forum and so can't post

How can i specify what fields i get from a

ctx.db.query...

, i extended my User and want to add something from that record to the jwt