user
02/16/2017, 12:54 PMuser
02/16/2017, 12:54 PMuser
02/16/2017, 12:55 PMuser
02/16/2017, 12:56 PMuser
02/16/2017, 12:58 PMuser
02/16/2017, 12:59 PMuser
02/16/2017, 1:00 PMuser
02/16/2017, 1:01 PMuser
02/16/2017, 1:01 PMuser
02/16/2017, 1:01 PMuser
02/16/2017, 1:02 PMcurrentSlide{
id
lesson{
id
slides {
id
}
}
}
user
02/16/2017, 1:02 PMuser
02/16/2017, 1:04 PMuser
02/16/2017, 1:05 PMuser
02/16/2017, 1:07 PMuser
02/16/2017, 1:07 PMuser
02/16/2017, 1:08 PMdzello
02/16/2017, 4:38 PMnilan
02/16/2017, 5:42 PMnilan
02/16/2017, 5:42 PMmikeroelens
02/16/2017, 6:33 PMsashko
02/17/2017, 12:25 AMnilan
02/17/2017, 1:02 PMcderue
02/17/2017, 2:28 PMsunrising
02/17/2017, 4:30 PMzebapy
02/17/2017, 5:29 PMfilter
for a node? Or is it some secret sauce 🙂tim2
02/17/2017, 6:21 PMaryan
02/17/2017, 6:42 PMexport default compose(
withRouter,
graphql(FeedQuery, feedQueryOptions),
graphql(userQuery, { options: { forceFetch: true }}),
)(Module)
if you look at the two graphql()
lines, those are both the data
portion of my compose. It seems like only the second one gets composed on my component. I'm guessing because props.data gets overwritten? What do you do when you have multiple datas?
One option I can think of is renaming the second one so it doesn't go into props.data, but not sure if that's the best/common practicearyan
02/17/2017, 7:15 PMaryan
02/17/2017, 7:15 PM