chore: update graphql dependency and use features

[totzk9]

graphql version 5.1.3 is almost 2 years old, since then numerous updates were made up until 5.2.0-beta.9 version which has more features and more control over the package

old:

new:

I created this PR for PGs who want to use the latest version of graphql package.

[dbarrosop]

Hello, thanks a lot for the PR. Just a bit concerned about the upgrade to a beta package but otherwise this LGTM.

[totzk9]

We can leave this PR as draft for now. I'll add a workaround in the issue while waiting for official release.
#143 (comment)

[dbarrosop]

Sorry, didn't mean to shutdown or delay this PR. If there is a good reason like "there is no further development in the 5.1 branch and this branch is missing much needed features" that might be a good reason to make an exception here. I was mostly trying to understand the rationale behind the use of a beta version so if you could explain a bit the situation that would help moving this PR forward. Thanks again for the work!

[totzk9]

@dbarrosop Hello
Yes, 5.1 is missing much needed features and it's been far from the lastest version but ultimately I do agree with you on why we should use a stable release. The beta version works for me but for the majority, it's better be safe than sorry on having such risk for everyone.

The latest beta release includes the timeouts, defaultPolicies and other configs I'm not familiar of but can be useful for others. It also allows better support for the latest Flutter versions and other dependencies

[dbarrosop]

Based on what you are saying and what I could see online I am leaning towards approving the use of this beta version. Looks like 5.1 is 22 months old which isn't too great. I will ask a colleague to review soon.

[dbarrosop]

Just a quick update, if by the end of Jan there isn't a stable release I think we should move forward with this PR

[dbarrosop]

I just checked and no release yet, I'd suggest updating the dep to v5.2.0-beta.10 and then me can merge.

Thanks a lot for the work here.

[totzk9]

Okay, will work on the dependency update

…

On Fri, 31 Jan 2025 at 7:52 pm, David Barroso ***@***.***> wrote: I just checked and no release yet, I'd suggest updating the dep to v5.2.0-beta.10 <https://github.com/zino-hofmann/graphql-flutter/releases/tag/v5.2.0-beta.10> and then me can merge. — Reply to this email directly, view it on GitHub <#144 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF2AUYQXEGBBQMXKMS3KKQL2NNPWHAVCNFSM6AAAAABQ366G4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRXGAZDMMZQHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[totzk9]

@dbarrosop would it be much better to increase the request timeout for it let's say 1 or 3 mins to avoid unexpected timeouts when devs updates to the new version?
They might have sudden timeouts when they haven't read the new changes

[totzk9]

note: the 5 seconds was taken from the default value of the dep itself

[totzk9]

another side note: we should probably wait for this PR to be merged then update the gql_websocket_link dep before we update to v5.2.0-beta.10

[dbarrosop]

for it let's say 1

yes, I think 1 minute is a much saner default

we should probably wait for this gql-dart/gql#475 to be merged then update the

sounds good to me

[dbarrosop]

@totzk9 thanks for the work. I approved running the CI and looks like there is some issues with dependencies (sorry that it took so long, I missed the github notifications, feel free to @dbarrosop when ready)

[totzk9]

@totzk9 thanks for the work. I approved running the CI and looks like there is some issues with dependencies (sorry that it took so long, I missed the github notifications, feel free to @dbarrosop when ready)

Yes I was aware of these CI failures, I was waiting for #144 (comment) to fix it.

[dbarrosop]

Ah, right, sorry, forgot about that one. Too many things to keep track of :P

[dbarrosop]

@totzk9 you probably saw but this was merged: gql-dart/gql#475 (comment)

[totzk9]

I haven't and thank you for pinging me. Will update do some tests on the PR

[totzk9]

I’m currently experiencing a kind of “dependency hell” due to how tightly coupled these packages are to each other. At the moment, running flutter pub get doesn’t work as expected because the required dependencies(nhost_gql_links, etc.) need to be published first. This makes it challenging to test or integrate the packages locally while waiting for all dependencies to be updated and published.

Is there a recommended approach for handling local development or testing in this scenario, especially when PRs span across multiple packages that haven’t been published yet?

[dbarrosop]

Mmm, I am not sure but I think the issue isn't related to the packages in this repo. I was checking and I think the issue is the following:

1. the new graphql version requires web_socket_channel ^3.0.1
2. the current gql_websocket_link requires web_socket_channel ^2.0.0

I saw this PR but I am unsure how far from merging is...

[totzk9]

I tried updating the gql_websocket_link to ^2.0.1 because it uses the web_socket_channel ^3.0.3

ref: https://github.com/gql-dart/gql/blob/7283180138e10d7ac2f9c0df96f0adb4951e1467/links/gql_websocket_link/pubspec.yaml#L14C4-L14C29

but I'm still getting some errors when doing flutter pub get