Any examples on how to do update mutations for entities that have linked datapoints would be greatly appreciated

I found this video series today about yoga + prisma:

from @Ben Awad

Created createUser Mutation after calling it from playground it returning an error. mutation{ createUser(firstName:"abc", lastName:"xyz", mobile:3453343443){ id } } error:- ctx.db.mutation.createUser is not a function"

@Dhiraj If you created your project with something like

graphql create {project_name} --boilerplate node-advanced

You must expose you mutation through

src/resolvers/index.js

I'm very much misunderatanding something with apollo server (I'm not quite sure of the exact library this syntax come from): Assume a Request model which has a many-to-one relationship named

kiosk

.

const existingRequest = await ctx.db.query.request({ where: { id } });

// only the base model is available here, not relationships:
existingRequest.kiosk // undefined

1. Which syntax does this come from? 2. Is there any doc for this syntax?

Hi, whenever I update Prisma I get a series of errors concerning my npm permissions:

gyp ERR! stack Error: EACCES: permission denied, rmdir 'build'

,

Error: EACCES: permission denied, mkdir '/Users/Wingding/Library/Caches/prisma

, and a few more. Have I corrupted my local folder permissions, or is anyone else running into these issues?

Hello guys

hi everyone 🙂

trying tho choose between graphqlyoga or "manual" implementation... what are the cons?

Hello all! May someone remind me again why we need to check the

generated

folder to Git?

anyone else having trouble creating a new cluster on prisma cloud?

Also, getting a lot of errors on the create cluster page and whenever I type, the page reloads

hey is there an easy way to transfer data from graph.cool console to the new prisma console?

anyone here tried to make a relationship of two type and the one type can’t be duplicate data?

Anyone know if the subscription webhook custom headers work? I'm sending an authorization header to my webhook endpoint, but the target isn't seeing it, so returns a 401 Unauthorized.

so, at the end of the day, the best place to put authorization is the businness layer?

Hi everyone. I would be really grateful if someone could help with that: https://www.graph.cool/forum/t/inconsistencies-with-self-relations/2593 It's been 3 weeks, and I'm still not able to get self-relations to work properly with Prisma (it was working on graphcool). Thanks!!

Limited to 1 req/s

is this ever gonna be reconsidered? I’m so far only using prisma for pet projects, but it makes the experiences really poor (page load takes several seconds as I do SSR and preload some data (that requires several reqs))

it would be nice if the “Free” tier was a viable option when you have a hobby project and as soon as/if you get some users you could upgrade.

even like 5 reqs/s would enable you to actually bootstrap something on it before spending money

Or more like 3600 requests an hour as upper limit and then a 5 requests per second limit. Then you can do quick bursts of 5 req/s, but if you do that for longer periods you hit the second cap

idk, something like shared usage would be nice

so if the cluster is not doing anything you can get all the requests you want

but if other people also use it it gets load balanced

@KATT @hvdklauw @harmony

Do you guys have any plans to make local development any easier?

Using the Graphcool Email/Password Authentication. What’s the proper way to handle logout/signout?

502 on the prisma service... anyone? 😛

I'd like to have required fields and queried fields returned by the bindings. Is there any way to do that? e.g. I'd like the

id

to always be returned, so ideally, I'd like to combine these into one...

db.query.users({}, `{ id }`)
   db.query.users({}, info)