Is it possible to use a returned value from the first query in a mutation call, and use it as a variable in the second query?

createUser(
      authProvider: {
        email: {
          email: $email,
          password: $password
        }
      }
    ) {
      id // this should be used as $userId in 'createHandler'
    }

    createHandler(
      firstName: $firstName,
      lastName: $lastName,
      email: $email,
      userId: $userId // <-- this one
    ) {
      id
    }

I would like to clone a project in the EU region to a new project in US West. Is that possible?

graphcool is refusing to delete data - I press the delete button, but the data does not get deleted. What should I do?

Is there an easy way to insert mockup data into graphcool?

playground

@oxyoxy88 https://console.graph.cool/<project_name>/playground

How do I pass the correct parameters to

updateOrCreateRSVP

? The

UpdateRSVP

input is required, and also has a required

ID

. So, I can't figure out how to call this mutation without already having an ID, which is a catch 22 for the first time I call it 😕

I can split this up over two different mutations (

createRSVP

/

updateRSVP

), but the Apollo code that is way too verbose 😞

I figured it out! Pass an empty string

""

, not

null

for the

update

!

{
  "id": "",
  "eventId": "cj7bsje03naa9015947x8yvld",
  "userId": "cj7flbi7rpd620112ouuim79l"
}

Thanks duckies! 🎉

Opened a PR against the docs: https://github.com/graphcool/content/pull/290

👋

I noticed PRE_WRITE function hook is deprecated... if I need to synchronously call an external API and then update the payload written to graphcool, is the best option now to use the TRANSFORM_ARGUMENT hook, or use a schema extension?

are permissions re-run for every sub-mutation inside a mutation? I have a

mutation

that contains 2

updateNode

operations on the same

Node

. The permission for the second

updateNode

is not satisfied until the first

updateNode

opperation has been applied, and I think this might explain why the second

updateNode

is failing...

Hey all, could I borrow someone for a few minutes to go through a problem I'm having? I can't figure out how to proceed 😕

any docs on what features

'use latest'

gives?

also wondering how the beta testing of the feature to use the graphcool file to control functions & permissions also is going?

@agartha commented on @Jess Telford’s file https://prisma.slack.com/files/U72FZLNB0/F72G32NF8/updateOrCreateRSVP.txt:

id: ""

Hello everybody, is there an option to do a

count query

? I want to receive the number of the posts… I don’t need their titles, ids or something like that 🙂

when I create a SSS in the UI and it asks me which object to use as the trigger, does that need to be accurate? can I just click next and then paste whatever subscription query in there?

reason being I'm going through and copying a lot of functions from dev to staging right now... if it needs to be accurate, might be a good idea to show it in the table of functions UI so I can make sure I haven't made any mistakes during the copy of functions

ah just ran into an odd issue, copying a graphcool file into a new environment...

[String!]

got transformed into

[String!]!

causing an issue with a mutation on the client-side, creating this error:

Variable '$tags' of type '[String!]' used in position expecting type '[String!]!'

So I was able to workaround by removing the

!

in the console and then use

graphcool pull

. huh - strange.

also I noticed upon graphcool pull the enums were moved, signalling perhaps that the

push

is not completely syncing the local file

Just got an email regarding the deprecation of PRE_WRITE. Did you send it out too early? “operationBefore” doesnt exist in my console / functions manager

(I know its TRANSFORM_ARGUMENT, just want to make sure im not missing anything)

You're not missing anything,

operationBefore

and

TRANSFORM_ARGUMENT

are identical, it's just a change in terminology that will take some time to be reflected everywhere (docs, console, ...)

Ok cool

Hi all I have a question for the chromeless npm package maintainers...