Thanks! 🙂 Yeah, I like to keep the sidebar’s themed to match the context. Helps a lot cause I’m in a few communities on my Slack Mac App haha

So much fun watching your launch fellas. Congrats on the amazing on-boarding experience and overall aesthetic and UX!

@bluetidepro How could i live without this theme before?Amazing! Thanks so much! 🙌

haha No problem @marcus 🙂

wowza, I finally feel at home @bluetidepro… 😮

for once life just started to make sense

I’m thinking that custom theme I made is clearly grounds for a lifetime

Growth

membership, right!? hahaha 😁

Grats on being #1 on hacker news all!

Congrats on the release! I'm excited to try it out on a project!

I give it 5 months tops before you get acquired by salesforce and then another month after that we will see the first “We just got acquired, here is our story”-presentation

@joar why not facebook? they are experienced with BaaS 😄

It’s not using machine learning enough

ok then let’s add functions that learn itself how to resolve

hey there @winwinwin @monestereo @mark.newman @wilson @fabianelias @cymen @aejnsn @marceli @cashshadow @esistgut @brumargues @jcmalone @mattam @alaindresse @drequeceler so awesome that you’re joining us today! 🙌 graphcool

in case you’re here for GraphQL-Europe, head on over to #graphql-europe-comm 🏃

Small thing, but if you have a relationship field named

items

, the create mutation wants an argument called

itemsIds

. Wouldnt

itemIds

make more sense?

I love this.

So it looks like there’s no out of the box support for polymer.

anyone else get error when trying to use CLI:

➜  ~ graphcool
/usr/local/lib/node_modules/graphcool/dist/src/index.js:33
const { version } = require('../../package.json');
      ^

SyntaxError: Unexpected token {
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:413:25)
    at Object.Module._extensions..js (module.js:452:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:475:10)
    at startup (node.js:117:18)
    at node.js:951:3

@brettc yes i got that, it's related to a wrong node version, everything before v6 can't do destructuring

if you have the npm package n, just use type n 6.0.0 in your terminal, fixed it for me

yeah i used

brew

to reinstall

node

solved it as well

ah was answered in the thread, didnt see it

cool 👍

Clearly you're more experienced with node than me. Thanks guys 🙌

http://prntscr.com/f8l8uw Yep, you could tell more as an introduction 😂

i get this when running the react-native-apollo-instagram example. what am i doing wrong?

@nilan commented on @marv’s file : hmm I'm not sure what's going on here

@nilan commented on @marv’s file : but I found this thread, maybe that helps? https://github.com/facebook/react-native/issues/13751