#graphql on the mind
-
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Replying to @methylene_
Really new to it but it looks really promising sofar! Im trying out
@apollographql and its great but it challenges alot of my current understanding of how to do things.. like having a#reactjs comp fetch its own data, when before this belonged in a container or store.2 replies 0 retweets 1 like -
Replying to @kviglucci @apollographql
with react apollo, the component is _still_ not fetching it's own data...it's either using a container created by `graphql` or leveraging the query component (which can also be thought of as a container, just using a render prop)
1 reply 0 retweets 0 likes -
Replying to @drunknhik @apollographql
Yeah thats fair. Right now i'm leveraging the Query component so the query just executes on mount. Im more used to having to manually manage a call to something like a redux action or a fn on a context, but I guess whats the difference?
1 reply 0 retweets 0 likes -
I think if the apollo client wasnt both the data store as well as the network layer, then it would feel more familiar. Though it seems really powerful this way where you let apollo manage all of your state as well as data access.
1 reply 0 retweets 0 likes -
Whats also really interesting is using link-state to also apply your local state to the client store and then use graphql to query it as well. Idk if I need graphql to tell me if a dropdown is open, but its cool that I can.
2 replies 0 retweets 0 likes
incredible. I thought I was joking when I said we’d use GraphQL in my game engine to query game state from the UI 
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.