do they have to be direct children?

no, it uses

context

just like

react-redux

so the

graphql

container has to be somewhere underneath the provider

ahh right, okay gotcha, thanks!

hi

was going through tutorial

render () { return ( <div className={classes.root}> <div className={classes.title}> {

There are ${this.props.viewer.allPokemons.edges.length} Pokemons in your pokedex

} </div> <div className={classes.container}> {this.props.viewer.allPokemons.edges .map(edge => <PokemonPreview key={edge.node.dataID} pokemon={edge.node} />)} </div> </div> ) } }

i am unable to use the id property as key

when i use edge.node.id the relay container doesnt have a key property.. i checked this in react console

when setting as edge.node.dataID the key property is available

could someone tell me why this happens ?

@abhisheksp Have you tried using

node.id

?

when i set key as

edge.node.id

the key property is not set , and react shows the warning that children in an array iteration require unique id ,

i checked this using react console and the Relay(PokemonPreview) component doesnt have keys

but when i use

edge.node.__dataID__

the key is set and is visible in the react console and the warning disappears

btw by react console i mean debugging tool for react in chrome browser

http://stackoverflow.com/q/40143763/5623786 Does anyone can help me out, please? Thanks. 🤓

@alex42 seems like in your

getVariables

you return

inviteAnswer

to always be

true

Also there’s a lot of inconsistent indentation and many superfluous semicolons 🙂 I guess you don’t have eslint set up, do you? 🙂

what's wrong with the semicolons?

they seem reasonable

In literal templates?

Im doing a hackathon today, any chance I can get an invite

Hey @jwaldrip Sign up at graph.cool and send me a pm with your email 🙂

are there any server side implementations out there that support stuff like this?

or if this is a bad idea, why? 😛

you can do this

query getArticlesAndUsers($limit: Int!, $user: ID!) {
    articles: allArticles (first: $limit) {
    title
    slug
    text
  }
  user: User (id: $user) {
    firstName
    lastName
  }
}

If I remember correctly, the queries are run sequentially from top to bottom.

does this suit your use case?

ok, I stand corrected. queries like this are run parallel simple smile