5 ms·
I really like the Apollo stack, but if you're thinking of using it in production right now, you should wait a little! There's a massive bug where if your graph
by maktouch 9y ago
I really like the Apollo stack, but if you're thinking of using it in production right now, you should wait a little!
There's a massive bug where if your graphql outputs 1 small error, the whole component does not get loaded.
Imagine a components that lists a bunch of items. If 19 returned correctly but 1 has an error, the "data" prop doesn't get passed, all you receive back is the error prop. It's pretty shitty for that.
https://github.com/apollographql/react-apollo/issues/1112 https://github.com/apollographql/react-apollo/issues/1112
Learned this the hard way :(
- jcun4128 9y agoDo you know which one is bad? Then requery and exclude the bad one?
- throwaway2016a 9y agoMeanwhile the top comment is saying exactly what I was trying to say and got upvoted... I obviously didn't articulate myself well.
- maktouch 9y agoThe kind of query where it fails (and where it especially hurts) is queries like `getLatestNotifications`. It would be a lot of cruft added to prevent this kind of bugs. So, yes, you know which one is bad, but it's not a query that's failing, it's something inside the result.