Great GraphQL presentation at React Native Berlin by Tim and Johannes

Thanks @olifante Are you planning to use GraphQL in a react native app?

not with React Native (at least not yet), but definitely with plain React, using Guillermo Rauch's amazing next.js

hello

Welcome @pkunwar and @dnalih :)

We are looking for a few people to beta test GraphQL subscriptions. send me a DM if you want to help out 🙂

hey folks. great talk yesterday 💯 I'll just be lurking and learning. don't mind me

Welcome @pedro 🙂

hi guys

Hi @dio!

graphcool is awesome!

Thanks! Glad you like it!

I notice that there's no vendor lockin right?

it's possible to run the api and console on our infrastructure?

we have a client with some hard requirements and build a graph server is not so easy

As of now it's not yet possible to run it on your own infrastructure.

thanks @schickling!

there's any plan to release it open source as you guys are saying on graphcool website?

Nothing official yet for our hosted backend. And yes, our console is completely open-source: https://github.com/graphcool/console

thinking through a use case where I have a wishlist that contain more than one type of object (products and hotels) - assuming that graphcool uses a relational store - is the best way to do this to create a generic “ListItem” schema? How best to relate that with the product and hotel objects?

@monkeybonkey If you have only few types of objects I would suggest creating an intermediary Wish model that has a one-relation to each of the objects. Does that make sense?

This is how we modelled a project for Twitter during EM where we needed to display a feed of events

@sorenbs so the wish model has optional links to the other types?… so there would just be some sparse data

Yes. It’s not ideal. but it’s the best we can do right now

sure, understood - I wonder if there is any way to guard against an error case where the wishobject somehow gets linked with two types of objects simultaneously

I guess I would just have to guard against that in code and not in the data model itself

Exactly. We are working on a way for you to add server side validation logic, which would make this a lot nicer, but for now I would just do that on the client. If it’s really important for you, you could add a mutation callback that verifies this and either alerts you or actively splits it up into two

I just saw your new landingpage 👏 👏 It looks really really good!

I'd say it looks cool 😉

but still renders old page on Twitter: https://twitter.com/semdubois/status/807177695255785472