Maina Wycliffe

Is there someone working on this? If no one, I would not mind tackling it.

@serendipity1004 We should probably expose the reset method, maybe at the client level, so you can invalidate the cache easily. And on a side note maybe we should switch to...

I think that would be amazing.

I am not sure, if you have any ideas, share them here and I will after some research we can compare notes. After that, you can get to work.

@serendipity1004 I agree, we should do something like that.

So, instead of just passing the data, we pass the QueryResults and the user checks for errors both?

Okay, I will work on this over the weekend.

I will work on this tomorrow, am thinking of adding a onError callback with a default method, which merges the GraphQLError list, one can override it to handle errors differently.

@micimize I started working on this and realized there was a PR on having [Library level exceptions](https://github.com/zino-app/graphql-flutter/pull/393). Can I work off this PR or should I wait for you to...

Have you tried stepping through the code using a debugger and see why the second request doesn't work. I will try and re-create your example when i get sometime tomorrow.