graphql-flutter VS dio

If you are a docs contributor, feel free to complete the website with the old docs that we had on https://github.com/zino-hofmann/graphql-flutter

Regarding the flutter + graphQL, found this graphQL client for flutter on Github.

- found Flutter graphql is way ahead , even almost mature as Apollo for JS. apollo-kotlin is several miles behind, a lot of issues, absolutely inconvenient usage after graphql-flutter

https://github.com/zino-hofmann/graphql-flutter/issues/894 looks like it is again maintained by other folks

My project needs to able to use Apollo-graphql in which it should support persisted queries . I found a package which can do graphql queries graphql-flutter. I had scrolled to the end and there's a feature of "PersistedQueriesLink" but tagged with "out of service".

There is an example here https://github.com/zino-app/graphql-flutter/tree/beta/examples/flutter_bloc

With no release in the last 6 months, piling up of issues and launch of a new fork (diox), I felt something was going on with dio. Sadly, today I came across an official announcement (updated on the project repo 2 days back):

You might want to think twice about dio....we evaluated dio on a recent project and decided to avoid it after running into a blocker when setting a custom timeout (this bug: https://github.com/flutterchina/dio/issues/1454)

- and Dio for http requests

I also had some troubles choosing which Dart HTTP client to use. I've started with dio, but when I tried to read one of our bigger JSON responses (~1.5mb) my browser tab froze (there seems to be an old issue describing the same behavior). After that I've switched to the default dart's http package and it is working fine but it doesn't have builtin requests abort/cancellation.