Cameron Nokes
Sep 24 · 1 min read

This is a great insight and I think sums up one of my main reasons for never wanting to use graphQL again — our front-end usually ends up needing a full domain model to function correctly. Dealing with constantly differing slices of the same data throughout an app is difficult to juggle and leads to lots of cannot read property 'whatever' of null bugs. For me and the use cases I’ve been exposed to, this design choice invalidates the whole “fetch only what you want” benefit that seems to be one of the primary reasons of using graphQL in the first place.

Cameron Nokes

Written by

Front-end developer and hamburger eater. Check out my screencasts:

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade