Hacker News new | ask | show | jobs
by dansingerman 2847 days ago
TLDR: You don't need to manage state in the client now; manage state in the server by making more API requests. And GraphQL makes that a bit easier. Oh and you still need to manage state in the client.
1 comments

Right? I fail to see how I can keep components all in sync across different parts of my app with GraphQL.

I'm already using Firebase, most of my operations are already unique API calls. I typically dispatch an update to my store and to firebase simultaneously in one thunk action. I typically dispatch the thunk directly from a connected component or from it's connected parent container. Seems like GraphQL solves literally no problems for me