-
-
Notifications
You must be signed in to change notification settings - Fork 448
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 to Dart 3 to compatibility with http ^1.0.0 #414
Conversation
Yeah.... I can't upgrade http package and packages depending on http. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi thanks for the nice PR. Also thanks for the cleanup throughout the code. However, this makes it a bit harder for me to spot the really important differences.
As far as I can see http 1.0.0 has no breaking changes, besides using new Dart 3.0 language features. So I think we can allow for http 1.0.0 without dropping support for 0.13.0 right? That makes it easier for others to upgrade in their own time.
I see you also dropped support for rxdart 0.26.0. Is there any reason for it? That version already is made with null safety looking at pub.dev. With a package it's always important to support as big of a range of versions as possible.
I agree with rxdart, and upgraded the rest to support null safety. |
Also check my PR for cached_network_image please |
flutter_cache_manager/example/lib/plugin_example/download_page.dart
Outdated
Show resolved
Hide resolved
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #414 +/- ##
===========================================
- Coverage 75.39% 75.18% -0.22%
===========================================
Files 22 22
Lines 691 685 -6
===========================================
- Hits 521 515 -6
Misses 170 170
☔ View full report in Codecov by Sentry. |
Analyzer and format issues fixed |
It might be helpful to update |
@renefloor, Is it worth updating build_runner min version to 2.0.0? Since previous versions support Dart < 2.12. |
I'm testing the code now on the oldest and newest Flutter versions, hope you don't mind pushing some fixes directly? |
No problem |
@renefloor Do you mind if I make some changes to delete unused rows in example to pass analysis? |
I'm currently also still making some changes, so maybe better to wait and not create (many) merge conflicts. It's too hard to keep the current minimum. I would have to allow flutter_lints 1.0.4, but that means that various developers can have different set of warnings. Setting the minimum to Dart 2.17.0 and Flutter 3.0.0, which are both over 1 year old. |
flutter_lines and other dev_dependencies dependencies do not affect the operation of package versions. That is, if dev_dependencies has the minimum version 2.17, and dependencies 2.12, then the package will have version 2.12. |
If anything, I would recommend putting a minimum 2.19 version of dart for the package. Since it is the last one that supports no-sound-null-safety. |
I expect so as well, but it did complain if I try to add it as a dependency in another clean project. |
@Carapacik it looks good to me now, you agree? |
Now yes |
I wonder if anybody will ever run this as real compiled app 😆 |
of course it will compile |
I meant for this change in the example: if (kDebugMode) {
print(error);
} |
@renefloor cached_network_image next? |
I now have to start really working, but probably can look at it tomorrow. I think it should work fine already though. |
There is still file ^7.0.0 used and there is an error with types somewhere. |
@Carapacik published flutter_cache_manager: https://pub.dev/packages/flutter_cache_manager/versions/3.3.1 |
Update dependencies
Update example to latest version
Fix analysis and format issues
Also update cached_network_image PR