Prisma

Hi! Any news on the subscriptions update?

<@U3WSHAM39> You can find the new subscription syntax here: <https://www.graph.cool/docs/reference/simple-api/generated-subscriptions-aip7oojeiv>

Does the still one still work? or do I need to rewrite existing subscriptions code?

You need to update existing subscriptions to the new API

I can help you with that if needed :slightly_smiling_face:

Thanks, but I’ve figured the new syntax out, just wanted to know if I had to go back and rewrite some code..

Yes, unfortunately. We're trying to keep breaking changes like this to a minimum, but in this case it was unavoidable. The new subscriptions API is stable :slightly_smiling_face:

it looks great.
Some breaking changes are ok now and then :smile:

A small tip would be to email that information to all customers though. a bit in advance.
As you might be done with the app and on to new adventures, then you need to plan time for the rewrite and might need some heads up

I agree! However, in this case we tried to communicate in advance that the subscriptions API will change soon. :slightly_smiling_face:

I might have joined in the small gap between communication and implementation then, or just missed the communication somehow.

Well well, not a big issue, I only have three subscribtion queries to rewrite.

Thanks anyway for your feedback :slightly_smiling_face:

“Client is not connected to a websocket.” I am gettting this message in playground

<@U4892L076> this is part of the subscription update, we're currently redeploying the Console

So when can i play with it :slightly_smiling_face:

in a few minutes! I'll notify you when the deploy is finished :slightly_smiling_face:

oh, that’s what is going on with the websockets! :sweat_smile:

ah, one more thing <@U40UPNC85> the new URL to subscribe to is  `<wss://subscriptions.graph.cool/v1/__PROJECT_ID__>`. Note the new */v1/*

Hey <@U4892L076> you can use the playground with subscriptions again :slightly_smiling_face:

Pardon, can you confirm if I use "updatedFields_contains” correctly? Because as soon as I add this field my subscription stops firing.

-.js

Without this field the received object contains updatedFields with item “pointer”

<@U3WSHAM39> can you share the according mutation?

mutation SetPointer($classroomId: ID!, $pointer: Json){
	updateClassroom(id: $classroomId, pointer: $pointer){
		id
		pointer
	}
}

Thanks Alex, I can reproduce this issue. Let me get back to you about that!

Thanks again, we were able to fix this issue. Should be deployed soon :slightly_smiling_face:

I just want to say that Graphcool is awesome, using the console is so easy and fun, great work :clap: :clap:

Am I missing something or.... are permissions "authenticated or not" or could I actually have node-level permissions based on user

<@U4BF8DHB4> Hey Nick! That's what our advanced permission system is used for. We're currently running it in our beta program.

Let's discuss in PM :slightly_smiling_face:

Anyone working with react-native and Auth0? I have problems with storing and retrieving the token

<@U4AFED3JP> in this example <https://github.com/graphcool-examples/exponent-auth0-instagram-example> we're using AsyncStorage. Should be similar on RN

I saw that example but I can't making it work, the problem I think is because is async

In my main component I retrieve the user and the token is not in the header yet

This is a contrived example on how I’m doing it
<https://gist.github.com/kimf/39da63aa4c26d3b230f1a4a7220819d5>

not using Auth0, but the principle should be the same I guess?

I’m using RN, Auth0, Apollo but I also used Redux and just persisted/hydrated the store

hello and thanks for the invitation :slightly_smiling_face:

<@U4BLH73HA> Cheers! Feel free to ask if there's any questions

Is the convention for `Models` to be singular or plural? For example, I have a `User` model, but also a `Purchases` model.

<@U3QTFRHK7> Great question! model names are assumed to be singular

so querying a single user can be done using the `User` query

querying multiple users can be done using `allUsers`

I can't seem to figure out How to use graphQL `interface`s in graph cool? Whats the best policy on this?

Hi folks. I get an error
WebSocket connection to ‘<wss://subscriptions.graph.cool/&lt;&lt;PROJECT_ID&gt;&gt;>' failed: Error during WebSocket handshake: Unexpected response code: 404. Anyone else experiencing this? What do I miss?

<@U439KMVCN> They have upgraded the subscriptions. the new url are `<wss://subscriptions.graph.cool/v1/__PROJECT_ID__>`. Note the new */v1/*

And the docs are here: <https://www.graph.cool/docs/reference/simple-api/generated-subscriptions-aip7oojeiv>

Hey <@U439KMVCN> the proper url is `<wss://subscriptions.graph.cool/v1/&lt;&lt;PROJECT_ID&gt;&gt;>`

Hi friends. I was trying to add a relation between 2 of my models but it seems to make all info currently in those models inaccessible. It shows the number of nodes in those models but the nodes are not visible and an error displays when I try to view the pages that says `cannot read property ‘viewer’ of undefined`. Any thoughts?

<@U447LHCA2> Cheers! This behaviour occurs when you have a field name like "userId" for example and now are adding a related field "user"

Ah that is the case, so if I remove that field I can add the relation successfully?

Nice, thanks man, I’ll let you know how it goes

It worked as expected, thanks for the help!

Hey everyone <!here|@here>, we're super excited about releasing our new GraphQL Subscriptions API! :rocket: Looking forward what awesome stuff all of you will build with it :raised_hands: <https://www.graph.cool/blog/2017-02-28-introducing-graphql-subscriptions-in4ohtae4e/>

Here is an example of the subscriptions btw: <https://demo.graph.cool/worldchat/>

Great timing on that release, just as we're implementing chat in our app

<@U4892L076>: When you create a subscription, you simply call it again, and that stops it.

Notice the `this.stripeTokenSubscription()` in the middle.

```
this.stripeTokenSubscription = this.props.data.subscribeToMore({
        document: receiveStripeId,
        variables: { userId },
        updateQuery: (previousState, { subscriptionData }) =&gt; {
          console.log('Purchasing...')
          // Now that user has a Stripe customer Id (ie. subscription has been triggered), make a purchase by creating a node in Purchase model.
          this.props.createPurchase({ variables: { userId } })
            .then(() =&gt; {
              console.log('Purchase complete')
              // Cancel current subscription
              this.stripeTokenSubscription()
            })
            .catch((e) =&gt; { console.error(e) })
        },
        onError: (err) =&gt; console.error(err)
      })
```

See here for more information: <https://medium.com/@ConsciousApps/integrating-stripe-with-react-graphql-and-apollo-client-e09fdc9e5b95#.rrn3jo1wr>

How does this compare with Scaphold subscriptions? (<https://scaphold.io/community/blog/build-realtime-apps-with-subs/>)

<@U1KPM2B9U> That's indeed a good and valid question. As I am a part of Graphcool, this answer will probably be opinionated, but I try to stay as objective as I can. First of all, we’re in contact with Scaphold and highly respect the work they’re doing.
Both Scaphold and Graphcool had subscriptions out there now for months, Graphcool however in beta, so we could iterate over our Implementation more easily. What you see now is the 2nd iteration of our API.
And now a feature breakdown:
In Scaphold and Graphcool you can subscribe to multiple mutations in one subscription query.
That allows you to write less code and maintain less subscriptions.
In Scaphold however, you can not distinguish the behavior of the subscriptions per mutation type.
Graphcool allows that by having the `mutation` on the level of the `filter`. People who are used to the `AND` and `OR` syntax know, which powerful filters you can write with that.

Scaphold supports basic scalar filters in their subscriptions.
However, as soon as you’re building a real big application, relational filters on subscriptions are a necessity.
Imagine you want to build Facebook and only get notified when a friend creates a Post, but not when someone else of the hundred millions of users post something.
As far as I can see, in Scaphold you currently can’t define a filter for that.
So before we released the Subscriptions it was very important to us to support that use case.
Graphcool not only supports scalar and relational filters in the subscription, but you can also combine the normal filters with subscription specific filters like `mutation_in` or `updatedFields_contains`.
That means in a chat you can say I am interested in all related messages and if the `text` of a message has been updated.
This is how you would express it with Graphcools API:

```
Message(filter: {
	node: {
		room: {
			name: "my chatroom"
		}	
	}
	mutation_in: [CREATED,UPDATED]
	updatedFields_contains: "text"
}) {
	mutation
	updatedFields
	node {
		id
		text
		author {
			id
			name
		}
	}
	previousValues {
		text
	}
}
```
There is much more to say, especially when it comes to our backend implementation, but I hope this could already give you an overview about the two implementations. In the next weeks we will release a blog article discussing our backend implementation of the GraphQL Subscriptions.

Hey guys, will you be providing a way to select the physical location of your data in the future? For instance, we are from Australia, so all of our traffic will have at least 180ms delay on top

<@U49V8B8TF> this is a feature we are currently planning. Is all of your traffic from Australia or do you also have international traffic?

Getting lots of "Uncaught (in promise) DOMException: Blocked a frame with origin "<https://console.graph.cool>" from accessing a cross-origin frame.”

<@U2Z3AS60H> is the console still working? Have you tried it in an incognito window with all extensions disabled? 

It seems to be working fine now :slightly_smiling_face: Thanks

whats the best practice for securing mutation callback endpoints. do i just add a query string secret?

i think a configurable basic auth header would be a good addition to callbacks

cool, you can add your voice here <https://github.com/graphcool/feature-requests/issues/118>

<@U4B67QF40> <@U4BU56TKP> welcome to our slack! :raised_hands: