Hey guys 👋 Does anyone know if there is any documentation for

connections

in Prisma API besides Schema itself? (I might have missed it in the docs as well 🤞)

How would you go about protecting parts of your schema? E.g. only revealing that a said query exists if the user provides a valid token? I just learned that schema directives existed yesterday and I'm pretty hyped about those. Currently using them for auth purposes. Would that be something that could solve that problem?

Currently, is there a resource collecting projects that are using Yoga + Prisma? Examples, open source projects, and the like. It’d be nice to create a public list of these if there isn’t one.

Anyone have a working example using Prisma/GraphQL-yoga and React-Apollo for File Upload? :s I keep getting rip by "Request disconnected during file upload stream parsing." I have tried googling but I feel stupid since I can't find the solution.

I wonder what made you guys go out and create graphql-yoga and prisma tooling around it? In the other examples referring to https://www.howtographql.com/ backend part You are using MVC frameworks like django and ruby on rails even Spring. in Node.js however there is a exiting MVC framework like sails.js but its not used here why?

Hey all 👋 This Prisma tutorial on how to deploy your prisma server to AWS Fargate was super helpful: https://www.prisma.io/docs/tutorials/-joofei3ahd. I'm wondering if anyone could point me to any docs/ tutorials/ recommendations on how to deploy your graphql server (i.e. graphql-yoga) to Fargate as well. I need subscriptions so I don't think Lambda is a great option in this case. I'd also like my graphql-server to live as close as possible to the prisma server (us-west). Any direction would be greatly appreciated. Thanks!

Is there a way to add a field along with the

info

object in prisma-binding? Basically, always add a field that should be grabbed regardless of the

info

object's contents.

I need to make such mutation from frontend:

input ActionMemberInput {
    personId: ID!
    side: String!
  }

  createAction(
    title: String!
    date: String!
    description: String
    karma: String!
    executors: String!
    members: [ActionMemberInput!]!
  ): Action!

That's schema from frontend:

export const CREATE_ACTION = gql`
  mutation createAction(
    $title: String!,
    $date: String!,
    $description: String!,
    $karma: String!,
    $executors: String!,
    $members: [ActionMembersInput!]!,
  ) {
    createAction(
      title: $title,
      date: $date,
      description: $description,
      karma: $karma,
      executors: $executors,
      members: $members,
    ) {
      id
      title
      date
      description
      karma
      executors
      members {
        person {
          id
          name
        }
        side
      }
    }
  }
`;

When I'm trying to make such mutation from frontend, I get error 404. I guess the problem somewhere there -

$members: [ActionMembersInput!]!,

(frontend schema) I tried to make same mutation from frontend and from playground and it worked in playground but didn't work in frontend

I tried to do something like this, but I don't completely understand how it works https://www.prisma.io/forum/t/how-do-i-add-an-array-of-objects-to-a-mutation-in-apollo-react/365/6

Ive added helmet.js to my server however when I look in the network tab in the first document has “X-Powered-By: Express” in the response header, so I think this means it’s not working properly? Does my code look OK? Thanks

const { GraphQLServer } = require('graphql-yoga');
const { Prisma } = require('prisma-binding');
const resolvers = require('./resolvers');
const authoriseToken = require('./other/auth');
const helmet = require('helmet');

const server = new GraphQLServer({
  typeDefs: './src/schema.graphql',
  resolvers,
  context: req => ({
    ...req,
    db: new Prisma({
      typeDefs: 'src/generated/prisma.graphql', // the auto-generated GraphQL schema of the Prisma API
      endpoint: process.env.PRISMA_ENDPOINT, // the endpoint of the Prisma API (value set in `.env`)
      debug: true, // log all GraphQL queries & mutations sent to the Prisma API
      // secret: process.env.PRISMA_SECRET, // only needed if specified in `database/prisma.yml` (value set in `.env`)
    }),
  }),
});

server.use(helmet());

<http://server.express.post|server.express.post>('*', authoriseToken);

server.start(() => console.log('Server is running on <http://localhost:4000'>));

Hey all, is it possible to access query/mutation arguments in a directive resolver?

For example I want to implement a directive resolver

isPostOwner

. How would I get the

postID

from the query/mutation?

do I have to do something in particular to get the generated prisma graphql schema updated on deploy?

How does prisma deal with race conditions in read-then-update -kind of mutations? All I could find was someone else asking the same, but no answers: https://www.prisma.io/forum/t/best-way-to-add-1-to-a-model-field-on-prisma-db-binding/3333

Hey everyone! I’d like to build real time collaboration into an app I’m building. So multiple people would be able to edit inside the same text field, add to a list of photos and change their order, etc. I’m trying to figure out the best way to implement this, specifically how to handle conflict resolution for two edits made at the same time (or someone editing offline and then getting connected and syncing when other changes have been made by others in the mean time). I had heard that aws appsync has conflict resolution, but I’m curious how I can achieve this using Prisma. Thanks!

Has anyone built a chat messaging system on top of Prisma?

is there any way to make something like this in schema:

type ActionMember {
  id: ID! @unique
  person: Person! || User!
  side: String!
}

Something like OR operation

Is increment/decrement feature still on roadmap or alr shipped? https://github.com/prismagraphql/prisma/issues/266

Looking at this image is it possible to see the SQL query executed under the hood.

A file was commented on

Hi, guys! Currently, Prisma GraphQL database WebSocket endpoint supports only subscriptions, but not queries and mutations. I've opened https://github.com/prismagraphql/prisma/issues/2607. If I use Apollo Server, I can create a full WebSocket transport that handles all type of GraphQL operations over the WebSocket (https://github.com/apollographql/subscriptions-transport-ws#full-websocket-transport). I did not fully understand the relationship between

prisma

,

graphql-yoga

and

apollo-server

. According to `graphql-yoga`'s docs,

graphql-yoga

is based on

apollo-server

. Right? Since

apollo-server

supports full WebSocket transport, why

graphql-yoga

don't?

Since

graphql-yoga

is based on

apollo-server

and Apollo Server 2.0 currently is in release candidate stage (https://github.com/apollographql/apollo-server/releases), does this mean that when the Apollo Server 2.0 stable version is officially released, I will be able to use all new mind-blowing features (such as https://dev-blog.apollodata.com/easy-and-performant-graphql-over-rest-e02796993b2b and https://dev-blog.apollodata.com/automatic-persisted-queries-and-cdn-caching-with-apollo-server-2-0-bf42b3a313de) that Apollo Server 2.0 offer directly in

graphql-yoga

?

is there any prisma community in discord?

If I wanted to relay to my Yoga server a particular data type with all the ORM-like GraphQL operations created by Prisma, what would be the best approach? As in exposing a subset of the Prisma-generated GraphQL schema through my own schema in Yoga.

I want to use graphql to replace an existing API and I am struggling with how to model the existing response. The API currently returns a list of things that can be of three types: Thing1, Thing2 or AlertThing. There may not be an AlertThing, but if there is, there is only one and it is the first item in the list. Any suggestions how best to model this? Should the schema enforce the list item types (and, if so, how??)? Or should the schema be a a bit more relaxed and simply define the result list as being comprised of the three types and have the resolver enforce the "AlertThing-first-if-any" rule? 🤪

I have such subscription:

Subscription: {
    personUpdate: {
      subscribe: (parent, args, context, info) => {
        return context.prisma.subscription.person({}, info);
      },
    },
  },

How can I detect was person created or deleted on the frontend? I receive completely same data when person was created or deleted

I push

person

into array of

persons

anytime I receive data from the backend, even when person was deleted because Idk how to detect is this person deleted or created so my application works not how I expect

where r docs for Cascading Deletes?

Guys, can u help me with cascading deletes, please? https://www.prisma.io/forum/t/help-with-cascading-deletes/3878

Hello, is it possible that any of Graphcool service developers take a look on my thread ? Thnx https://www.prisma.io/forum/t/graphcool-update-and-create-mutation-behaving-differently/3853