Hello. 👋

hey!

💯 @thisismissem

@thisismissem when you want things that you know will work you choose erlang

anything written in erlang can run for centuries 😄

@codepreneur not necessarily.

Things written in erlang tend to only last for centuries because of the people that write erlang

(i.e., you could say the exact same thing about languages like cobol and such)

graph.cool clearly tries to be the next firebase 😄

The main page says that serverless functions for fine grained permissions are in beta. Is more information about that available? I need to be able to set up table and row level permissions for individual users as well as roles.

Hi Cullan. It sounds like what you want can be achieved with Permission Queries. @nilan will reach out to you when he is back in the office with more information.

@sorenbs Thank you. I am pretty impressed so far. Nice work on the intro tutorial.

Hey <!everyone>! We have exciting news: 🎉 We’ve just announced GraphQL-Europe - Europe’s first GraphQL conference (it’s non-profit btw). As many of you are actually based in Europe, we thought this might be a fantastic opportunity to meet everybody and learn more about GraphQL graphql https://graphql-europe.org/

nice… i already signed up.

@schickling how much ?

The tickets (including prices) will be available during February.

what is your estimate? or you dont know (about the prices)

cause it depends on how many people signup/give talks ?

and on sponsors?

Signed up too

We just implemented support for Apollo Query Batching on Graphcool. If anybody <!here|@here> is using Apollo and curious about optimising your performance I would love to talk to you 🙂

@schickling : signed up too !!

So I am trying to log in a user with this mutation:

const LoginUserMutation = gql
  mutation signinUser(email: {$email: String!, $password: String!}){
    signinUser(email: {email: $email, password: $password }) {
      token
    }
}

Except when ever I run my app I get the following error:

Uncaught Error: Syntax Error GraphQL (2:23) Expected $, found Name "email"

1: 
2:   mutation signinUser(email: {$email: String!, $password: String!}){
                         ^
3:     signinUser(email: {email: $email, password: $password }) {

I understand that it wants a $email on line 2 but then how does the mutation know which

$email

I am referring to on line 3?

can you rename your

$email

variable to something else please? curious to see if that fixes it

cc @charlieroth

Doesn’t it have to be named that since I am using the Email auth provider?

a variable can be named however you like

the field you assign it to has to be called

email

, yep

Oh okay I am just going off the code snippets in the docs