perhaps someone from graphcool can advise

perhaps there's a better way

@picosam functions as part of the Request Pipeline are "synchrous" in that sense. Functions as part of a server-side subscription are "asynchrounous" in that sense.

That means, functions in the RP block/delay the mutation from the client perspective

if your RP function runs 100ms, your client will receive the mutation response 100ms later your SSS function has no impact on the mutation response time

Very clear, thanks 👍

thanks @nilan

sss rocks

were you guys at react-europe?

it would have been a blast to have graphcool there

sadly, we were busy doing the last preparations for GraphQL Europe 😱

Sorry @nilan, have been not keeping track of latest developments much. Can you use graphcool‘s latest server-side functions as replacement for, say, external server & mutation callbacks (like I’ve written about here: https://medium.com/consciousapps/integrating-stripe-with-react-graphql-and-apollo-client-e09fdc9e5b95)?

hey @nilan, @schickling has invited me here ... I'll let you guys know when I find something that's off on the website and anywhere

@nilan it seems there's some strange things going on with the inline functions editor

Functions inline editor bug

so the code snippet above works

but the following fails

The two snippets above are equivalent in functionality, differing only at line 18 in terms of syntax: one line vs multiline if statement

losing hair fast

i could be doing something wrong

I'm not sure if this is intended or not, but I think there might be something weird. In the console page, when enabling an Integration (I tried authentications only so far), the page reloads. It gives a feel of an HTML <form> that does a POST because there was no event.preventDefault() called before the handler returned. I also used to get this when using React as my frontend, and I realized later that it was because I was only calling event.preventDefault() after my processing, and because it immediately reloads the page, I could not see that it was never called because there was something that caused exception in earlier calls, and the handler didn't return false nor prevented the default behavior, so the POST fired as expected, causing a page reload. Probably also because of buffered console, which caused delays before I could see anything on the dev console, I mean, it's not straightforward to debug.

I might be wrong, but it certainly felt that way

@nilan This also happens when I Disable an integration. And indeed, I could see some errors in the console right before the page reloads. So, definitely something that can be fixed there.

Guten Abend! Just to be sure: if I have permissions set on different fields and I would like to fetch those fields or not depending upon the role of the person querying, I should simply use directives, right?

@nilan – Are there goo generic admin ui/tool for connecting to GraphQL databases ? Similar to the web ui for MySQL and other SQL-Like databases ?

Anyone in here have expereince with

apollo-connect

and using it to

mapQueriesToProps

with Redux?

@nilan I'm trying-out subscription, and I'm always getting an

error

after a few seconds. What should I look for to solve it? I'm new to the concept of GraphQL, and I'm not sure if I'm doing something wrong. I have reduced the subscription to bare minimum, and I still get the same error message that contains absolutely no error message whatsoever

@nilan commented on @eliezedeck’s file https://prisma.slack.com/files/U5M2KE6P5/F5LMMT41E/subscription_error__cj3eqcbi92ib00175qi9kicfo_exists_.php: is this in the Playground or in your app?

Playground