Signup mutation doesn't work with example in the readme. User will receive error in the Playground because 'name' is a required field.

Two possible solutions:

1. Change the schema.graphql file's 'User' definition to be:

type User {  
  id: ID!  
  email: String!  
  name: String  
}

-- OR --

2. Change the README.md example mutation of 'signup' to include a name argument.

mutation {
  signup(name: "Alice" email: "[email protected]", password: "graphql") {
    token
  }
}

I guess it is not open source yet, but I really wish to check it 🙏

I would love to see an example implementing GraphQL-based microservices with different databases and of course using an API gateway as the main entry point for client apps.

I suggest to add it into the official documentation or host it on "examples" folder in this repository.

Remove "esnext.asynciterable" from compilerOptions.lib[] in tsconfig.json and prepend src/generated/index.ts by:

/// <reference lib="esnext.asynciterable" />

We should add some Thrift + Prisma examples.

Hi prisma team, is it possible to put the docker-compose file in the go-graphql example instead of the one with prisma deployed endpoint ? Plus I have a lot of errors with the generated code when switching to my own prisma server with the way you scaffolded it as it is not scaffoled like this with gqlgen init.

Hi guys, I'm learning graphql so I borrowed a schema from this tutorial and I encountered an error after using the command gqlgen -v

/home/sacha/go/src/prisma-go-hackernews/tmp/resolver.go
/home/sacha/go/src/prisma-go-hackernews/prisma-client/prisma.go:5046:6: VotesParamsExec redeclared in this block
/home/sacha/go/src/prisma-go-hackernews/prisma-client/prisma.go:3250:6: 	other declaration of VotesParamsExec
validation failed: couldn't load packages due to errors: prisma-go-hackernews/prisma-client

Did I miss something specific to prisma datamodel like relations ? Let me know if you have the same error or not, here is my repo to reproduce the error the behavior

P.S. Sorry if I posted my issue in the wrong repo

We should replace the seed.graphql files with more language-idiomatic seed scripts using the generated Prisma client.

IMO removing the restart policy is what we should do (and so allow services to crash), restart: on-failure on the opposite, would just hide any problem by restarting servers (db or prisma) without any notice from the dev.

WDYT?

related PR #44

That can either happen using subscription functions, or logic directly in the resolver code.

Pending until prisma/prisma#3066 is completed.

I want to add a avatar field to Type User,but I do not know how to upload pictures to local system,could the examples show this feature?

• flow-graphql
• flow-script
• go-graphql
• go-rest
• go-raw-db-access [ON HOLD]
• node-cli-app
• node-graphql
• node-graphql-auth
• node-graphql-auth-advanced (should include permissions-with-shield)
• node-graphql-subscriptions
• node-graphql-schema-delegation
• node-script
• node-rest-express
• node-raw-db-access [ON HOLD]
• typescript-cli-app
• typescript-graphql
• typescript-graphql-auth
• typescript-graphql-auth-advanced (should include permissions-with-shield)
• typescript-graphql-subscriptions
• typescript-graphql-schema-delegation
• typescript-script
• typescript-raw-db-access [ ON HOLD]

• Add CI tests for types (#37)

• Add CI tests for running examples against a real Prisma (say using Prisma+CircleCI) (#37)

• Make the start command fail, if the type check fails
  -- One known anti-instance for this is flow (there may be more), where yarn start works but yarn flow fails

• Add prettier lint to all JS based examples by adding it to yarn test

• One Prisma server for all examples, individual example folders should not have CI code but the circle configuration at the root should cd into the respective folder and execute

• Ideally, a CI build should run per example, only when files of that examples are changed (can be done later, but we need to persist this in form of a separate issue)

In most cases your domain model and database model is not a 1:1 mapping but includes some computed/derived values which are implemented using "custom resolvers". To make this distinction clearer, we should add a few computed values to the domain model for the GraphQL examples.

Adding /* GraphQL */ comment allows syntax highlighting:

Before

After

WDYT?

The *-graphql-auth examples (e.g. typescript-graphql-auth) should be based on the *-graphql examples (e.g. typescript-graphql) and extend their GraphQL schema/datamodel.

• Remove yarn prisma script usage for JS-based examples (more context here)
• Add instructions how to install correct Prisma CLI (beta if needed)

problem is here:
https://github.com/prisma/prisma-examples/blob/master/go-script/main.go#L5

cd /Users/apple/workspace/go/src/github.com/prisma/prisma-examples/go-script && go get ./...
package go-gin/prisma-client: unrecognized import path "go-gin/prisma-client" (import path does not begin with hostname)
make: *** [dep-more] Error 1

I think you should have the full path

Hi,
Could you please provide an example on generating REST api client side subscription using Prisma Client's $subscribe?

I cant figure out a way to properly listen to CRUD events using $subscribe.

const el = await prisma.$subscribe.message().node();
el.next().then(e => console.log(e)); // <-- This only works for the next event, how can i listen to all future events instead?

Would you consider supporting Dart CLient too ?

Dart Lib for graphql
https://github.com/zino-app/graphql-flutter

Example
https://github.com/zino-app/graphql-flutter/blob/master/example/lib/main.dart

I use this with a graphql Golang server based on GQLgen now and its nice and clean flow.

Issue

• Followed the steps to get node-graphql-auth up and running, but upon trying to do mutation signUp, I get the following error:

dyld: lazy symbol binding failed: Symbol not found: __ZN4node19GetCurrentEventLoopEPN2v87IsolateE
  Referenced from: /Users/TD/Documents/Projects/GraphQl/prisma-examples/node-graphql-auth/node_modules/bcrypt/lib/binding/bcrypt_lib.node
  Expected in: flat namespace

dyld: Symbol not found: __ZN4node19GetCurrentEventLoopEPN2v87IsolateE
  Referenced from: /Users/TD/Documents/Projects/GraphQl/prisma-examples/node-graphql-auth/node_modules/bcrypt/lib/binding/bcrypt_lib.node
  Expected in: flat namespace

This causes problems when transpiling the typescript code to another folder like ./dist.

It would be nice to also have the complete story in the examples, i.e., compiling and running the code in production because ts-node is not intended for production.

The example permissions-with-shield is using prisma-binding,Could use prisma client instead of prisma-binding in next version?

https://github.com/prisma/prisma-examples/tree/master/archive/permissions-with-shield

Right now, it seems like it's only possible in the golang generated client code to query for an object OR it's relation, not both. This seems possible in the Typescript as such:

const linksByUser: LinkNode[] = await prisma
  .user({ email: "[email protected]" })
  .links()

It would be useful if were possible to get a single object AND a relation(s) in a single query (is this not a main purpose of GraphQL?) rather than just one (the object) or the other (the relation)

There has been some discussion about how to throw errors from resolvers properly.

An example that show cases different approaches that are considered best practice would be super helpful!

If anyone's interested in contributing such an example, feel free to ping me in Slack (my handle there is @nilan), happy to collaborate on this one! 🙌

We should add some gRPC + Prisma examples.

Would it be possible to restore this example?

https://github.com/prisma/prisma/tree/master/examples/archive/file-handling-s3

Could update prisma-binding with prisma client in permissions-with-shield example?

Is this working also in Browser? I do not see any examples.

• Add CI tests for types

• Add CI tests for running examples against a real Prisma (say using Prisma+CircleCI)

Gin is one of Go's most popular web frameworks. We should add an example of how to use Prisma together with the Gin framework. (See forum thread.)

I tried to run masters query from node-graphql-schema-delegation example playground but I got this error:

Server is running on localhost:4000
TypeError: Cannot read property 'query' of undefined
    at masters (/home/ubuntu/workspace/prisma-examples/node-graphql-schema-delegation/src/resolvers/Query.js:2:56)
    at resolveFieldValueOrError (/home/ubuntu/workspace/prisma-examples/node-graphql-schema-delegation/node_modules/graphql/execution/execute.js:531:18)
    at resolveField (/home/ubuntu/workspace/prisma-examples/node-graphql-schema-delegation/node_modules/graphql/execution/execute.js:495:16)
    at /home/ubuntu/workspace/prisma-examples/node-graphql-schema-delegation/node_modules/graphql/execution/execute.js:364:18
    at Array.reduce (<anonymous>)
    at executeFields (/home/ubuntu/workspace/prisma-examples/node-graphql-schema-delegation/node_modules/graphql/execution/execute.js:361:42)
    at executeOperation (/home/ubuntu/workspace/prisma-examples/node-graphql-schema-delegation/node_modules/graphql/execution/execute.js:289:122)
    at executeImpl (/home/ubuntu/workspace/prisma-examples/node-graphql-schema-delegation/node_modules/graphql/execution/execute.js:154:14)
    at Object.execute (/home/ubuntu/workspace/prisma-examples/node-graphql-schema-delegation/node_modules/graphql/execution/execute.js:131:229)
    at doRunQuery (/home/ubuntu/workspace/prisma-examples/node-graphql-schema-delegation/node_modules/apollo-server-core/dist/runQuery.js:124:42)

The current examples are based on a weird datamodel which looks like the following

type Cat {
  id: ID! @unique
  name: String!
  color: String!
  favBrother: Cat
}

type Master {
  id: ID! @unique
  catz: [Cat!]!
}

I suggest to base it on the following data model instead:

Minimal

type Post {
  id: ID! @unique
  isPublished: Boolean! @default(value: false)
  title: String!
  content: String!
}

Basic

type Post {
  id: ID! @unique
  createdAt: DateTime!
  updatedAt: DateTime!
  isPublished: Boolean! @default(value: "false")
  title: String!
  content: String!
  author: User!
}

type User {
  id: ID! @unique
  email: String! @unique
  password: String!
  name: String!
  posts: [Post!]!
}

This also means the resulting application should be adjusted to match the new datamodel.

For the node-graphql example, the createDraft mutation cannot be executed. For example, try to run this mutation:

mutation b {
  createDraft(title: "Title" content: "Content" authorEmail: "[email protected]") {
    id
  }
}

you will get the error message:

{
  "data": null,
  "errors": [
    {
      "message": "No Node for the model User with value '[email protected]' for email found.",
      "locations": [
        {
          "line": 8,
          "column": 3
        }
      ],
      "path": [
        "createDraft"
      ],
      "code": 3039,
      "requestId": "local:api:cjmal9soq000i0b83z8ckqei0"
    }
  ]
}

The reason is that no author exists yet. However, there is no mutation to create a new author either.
This should be cleaned up.

Current workaround: directly connect to the Prisma endpoint and create a new user:

mutation a {
  createUser(data: {
    name: "Nilan"
    email: "[email protected]"
  }) {
    email
  }
}

Then the first mutation works.

Open questions

• How to integrate demo server? (vs docker-compose.yml)

Hey all. After installing successfully the go-graphql example, opening http://localhost:4000 playground i try to create a new "draft":
mutation { createDraft(title:"Test title",content:"Test content",authorEmail:"[email protected]"){ id title content } }
i got the following error in go:
`interface conversion: interface {} is nil, not map[string]interface {}

goroutine 22 [running]:
runtime/debug.Stack(0x1, 0x0, 0x0)
/usr/local/go/src/runtime/debug/stack.go:24 +0xa7
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
go-graphql/vendor/github.com/99designs/gqlgen/graphql.DefaultRecover(0x8f02c0, 0xc000213f20, 0x806300, 0xc0001209f0, 0xc000136d90, 0x40d23f)
/home/dan/go/src/go-graphql/vendor/github.com/99designs/gqlgen/graphql/recovery.go:16 +0xa7
main.(*executionContext).FieldMiddleware.func1(0xc000368bb0, 0x8f02c0, 0xc000213f20, 0xc000137900)
/home/dan/go/src/go-graphql/server/generated.go:2461 +0x78
panic(0x806300, 0xc0001209f0)
/usr/local/go/src/runtime/panic.go:513 +0x1b9
go-graphql/vendor/github.com/prisma/prisma-examples/go-graphql/prisma-client.PostExec.Exec(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc0003dc7e0, 0x1, 0x1, 0x0, ...)
/home/dan/go/src/go-graphql/vendor/github.com/prisma/prisma-examples/go-graphql/prisma-client/prisma.go:2887 +0x14cf
main.(*mutationResolver).CreateDraft(0xc0001620a0, 0x8f02c0, 0xc000213f20, 0xc0002a6021, 0xa, 0xc0002a6038, 0xc, 0xc0002a6055, 0x16, 0x0, ...)
/home/dan/go/src/go-graphql/server/resolver.go:36 +0x5d2
main.(*executionContext)._Mutation_createDraft.func1(0x8f02c0, 0xc000213f20, 0xc000198030, 0xc000209898, 0x20, 0xc000209890)
/home/dan/go/src/go-graphql/server/generated.go:464 +0x232
go-graphql/vendor/github.com/99designs/gqlgen/graphql.DefaultResolverMiddleware(0x8f02c0, 0xc000213f20, 0xc000507720, 0x8f02c0, 0xc000213f20, 0xc000209900, 0xc000507720)
/home/dan/go/src/go-graphql/vendor/github.com/99designs/gqlgen/graphql/context.go:33 +0x3a
main.(*executionContext).FieldMiddleware(0xc000368bb0, 0x8f02c0, 0xc000213f20, 0x0, 0x0, 0xc000507720, 0x0, 0x0)
/home/dan/go/src/go-graphql/server/generated.go:2465 +0xa1
main.(*executionContext)._Mutation_createDraft(0xc000368bb0, 0x8f02c0, 0xc000213f20, 0xc00012c800, 0xc000213e30, 0x3, 0x3, 0x1, 0xc000507700)
/home/dan/go/src/go-graphql/server/generated.go:463 +0x1b2
main.(*executionContext)._Mutation(0xc000368bb0, 0x8f02c0, 0xc000213e60, 0xc000368800, 0x1, 0x1, 0x7f891d9706c0, 0x0)
/home/dan/go/src/go-graphql/server/generated.go:430 +0x589
main.(*executableSchema).Mutation.func1(0x8f02c0, 0xc000213e00, 0x8272c0, 0x80d801, 0xc0005076e0)
/home/dan/go/src/go-graphql/server/generated.go:390 +0x61
go-graphql/vendor/github.com/99designs/gqlgen/graphql.DefaultRequestMiddleware(0x8f02c0, 0xc000213e00, 0xc0005076e0, 0xc000142c40, 0xc000209be0, 0x42b072)
/home/dan/go/src/go-graphql/vendor/github.com/99designs/gqlgen/graphql/context.go:41 +0x3a
main.(*executableSchema).Mutation(0xc000150000, 0x8f02c0, 0xc000213e00, 0xc0003dc700, 0xc000213e00)
/home/dan/go/src/go-graphql/server/generated.go:389 +0xd8
go-graphql/vendor/github.com/99designs/gqlgen/handler.GraphQL.func1(0x8efec0, 0xc00048e2a0, 0xc000140c00)
/home/dan/go/src/go-graphql/vendor/github.com/99designs/gqlgen/handler/graphql.go:255 +0x562
net/http.HandlerFunc.ServeHTTP(0xc000119110, 0x8efec0, 0xc00048e2a0, 0xc000140c00)
/usr/local/go/src/net/http/server.go:1964 +0x44
net/http.(*ServeMux).ServeHTTP(0xbb6140, 0x8efec0, 0xc00048e2a0, 0xc000140c00)
/usr/local/go/src/net/http/server.go:2361 +0x127
net/http.serverHandler.ServeHTTP(0xc0001284e0, 0x8efec0, 0xc00048e2a0, 0xc000140c00)
/usr/local/go/src/net/http/server.go:2741 +0xab
net/http.(*conn).serve(0xc000150280, 0x8f0200, 0xc0001427c0)
/usr/local/go/src/net/http/server.go:1847 +0x646
created by net/http.(*Server).Serve
/usr/local/go/src/net/http/server.go:2851 +0x2f5
`
I thought that the fact that the user email did not exist, so i went to my prisma endpoint and create a user with that email successfully, and also create a test draft in the same prisma endpoint. Querying the playground for the draft gave me an empty response:

`{
drafts{
id
title
}
}

{
"data": {
"drafts": []
}
}
`
I have go 1.11 installed, prisma 1.17 and latest graph-cli

Need to move generated files into the generated folder.

Using yarn prisma can be confusing for new developers and often leads to many pitfalls. I suggest to remove the "prisma" alias from scripts in the package.json file. It's no longer needed once this feature lands.

Typescript is complaining here with: parameter 'req' implicitly has an 'any' type

Could fix with an ignore in the tsconfig.js like this: "noImplicitAny": false,, but I am not a typescript expert in any way shape or form ¯\_(ツ)_/¯

Hello,

I cloned this repo a little over an hour ago to play around with authentication. Specifically, I cloned the typescript-graphql-auth repo. Running it out-of-the-box with the commands specified in the README works fine, but when I try to run the signup mutation from the README

mutation { signup(name: "Alice", email: "[email protected]", password: "graphql") { token } }

I get the following error:

Error: Cannot query field 'createdAt' on type 'User'. (line 4, column 5): createdAt ^ at BatchedGraphQLClient.<anonymous> (MY_PATH\typescript-graphql-auth\node_modules\http-link-dataloader\src\BatchedGraphQLClient.ts:74:13) at step (MY_PATH\typescript-graphql-auth\node_modules\http-link-dataloader\dist\src\BatchedGraphQLClient.js:40:23) at Object.next (MY_PATH\typescript-graphql-auth\node_modules\http-link-dataloader\dist\src\BatchedGraphQLClient.js:21:53) at fulfilled (MY_PATH\typescript-graphql-auth\node_modules\http-link-dataloader\dist\src\BatchedGraphQLClient.js:12:58) at process._tickCallback (internal/process/next_tick.js:68:7)

I'm thinking this must be an issue with the codebase rather than something I've configured, since I've configured essentially nothing.

The following examples should be added for each language:

• GraphQL server with subscriptions
• Raw DB access

Hi great repo, 1.17 looks fantastic!

I have a real question: why do you attach prisma to context instead of doing a regular import of the instance?