-
-
Notifications
You must be signed in to change notification settings - Fork 623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade packages in graphql pubspec.yaml and graphql_flutter pubspec.yaml #1463
base: main
Are you sure you want to change the base?
Conversation
probably there is some regression? |
If I remove the line I'm unable to figure out why |
Unfortunatly I have not enough bandwidth to debug this issue, I do not want to promise that I will review, it because I am not in a good period, sorry! Probably if I were you I would upgrade one dependency at a time(and make a single commit per dependency and per graphql package) in this way you can isolate what is going wrong. |
I have run some tests and it seems the problem lies with web_socket_channel no longer setting closeCode. I was able to reproduce this easily with the same code working on version 2.4.5 and not working on 3.0.1 I have submitted an issue: dart-lang/web_socket_channel#383 |
@vincenzopalazzo I have had a look at the source code and Hence, I have removed The tests that check disconnect still have
The benefit of having a new version of graphql-flutter, supporting web_socket_channel 3.0.1 are that code bases can now be upgraded, since a lot of packages now require web_socket_channel 3.0.1 Hopefully this can be merged now? The only thing that will still need updating (not sure how to do that) is to fix this:
I will monitor dart-lang/web_socket_channel#383 and if they fix closeCode (or indicate where the problem lies), I will update the tests again to check for this and do a new PR. |
Upgrade packages in
graphql
pubspec.yaml andgraphql_flutter
pubspec.yaml to latest, where possible.