-
-
Notifications
You must be signed in to change notification settings - Fork 207
feat: Use cupertino http and websocket implementation #1145
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
base: main
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 14870387715Details
💛 - Coveralls |
@Vinzent03 we should make sure we run CI also on macOS, and test the package at least in a iOS build, just saw that we don't to that. I created an issue for tracking that, #1146 feel free to pick it if you want, otherwise I can work on it later. |
I'm pretty sure to verify the behavior of the cupertino http client we can't just run the existing ci on a macos build in ci. For iOS we need flutter integration tests to actually run them on a iOS simulator. For macOS I'm unsure if the cupertino http client works if we run widget tests or actually need integratino tests as well. So we would need to write many additional tests sa well. |
I see there is an Probably just getting all these examples built in CI, would already solve the issue with checking if the library works on all available platforms. |
Hey @Vinzent03 I just merged a few changes to CI, including builds on the macOS runner, can you rebase this PR? |
What kind of change does this PR introduce?
feature
What is the current behavior?
Uses the implementation from
dart:io
forhttp.Client
andWebSocketChannel
.What is the new behavior?
Use the classes provided by
cupertino_http
.Additional context
I do not own a mac, so I cannot test this. So we can hopefully find a person to verify this actually works on iOS and macOS.
close #147