Closed MagnusJohansson closed 11 months ago
@MagnusJohansson the problem is if I upgrade the http package every developer that is using this package must update their projects to dart 3.x
I think you can avoid that by doing an inclusive version range, something like:
http: ">=0.13.5 <2.0.0"
Developers who are using Dart 3 and http 1.x.x should be able to use your package, and legacy v0.x.x should still work.
I think you can avoid that by doing an inclusive version range, something like:
http: ">=0.13.5 <2.0.0"
Developers who are using Dart 3 and http 1.x.x should be able to use your package, and legacy v0.x.x should still work.
Personally I think the cleaner way would be to release a new major version 6.0 and bump the requirements in this release. That way it be more obvious to users upgrading the library that there are potentially breaking changes in this package or it's dependencies.
check 6.x.x
What version are you using?
5.0.11
What OS and version are you using to local deploy your application?
Windows 11
What platforms are you seeing the problem on?
Android
pubspec.yaml
Describe the Bug
Now that the http package is updated to version 1.0.0, please consider make this package compatible with the latest Dart 3 packages
Expected Behavior
This package should be compatible with Dart 3 packages
To Reproduce
Relevant log output
flutter doctor -v
Info.plist (iOS)
No response
Podfile (iOS)
No response
AndroidManifest.xml
No response
MainActivity.java
No response
MainActivity.kt
No response
index.html
No response
Info.plist (macOS)
No response