[Detrimental/Urgent] Versioning across libraries is or may become a nightmare (plans to resolve?) #20936
Description
I have the above issue since updating my Flutter version:
The current Dart SDK version is 2.1.0-dev.1.0.flutter-69fce633b7.
Because no versions of cached_network_image match >0.4.1+1 <0.5.0 and cached_network_image 0.4.1+1 depends on flutter_cache_manager ^0.1.1, cached_network_image ^0.4.1+1 requires flutter_cache_manager ^0.1.1.
And because no versions of flutter_cache_manager match >0.1.1 <0.2.0 and flutter_cache_manager 0.1.1 depends on uuid ^0.5.3, cached_network_image ^0.4.1+1 requires uuid ^0.5.3.
Because uuid 0.5.3 requires SDK version >=1.0.0 <2.0.0 and no versions of uuid match >0.5.3 <0.6.0, uuid ^0.5.3 is forbidden.
Thus, cached_network_image ^0.4.1+1 is forbidden.
So, because sellquick_app depends on cached_network_image ^0.4.1+1, version solving failed.
pub get failed (1)
The above is just an example, but lately I have found myself downgrading/upgrading/tuning library versions - up to this point - and think it important to raise awareness, if it can be talked/brought into next step architecture considerations for Flutter. I am familiar with Android development and aware that Gradle has capacity to control transitive dependencies e.g. implementation and api keywords.
Are there plans to bring this Gradle style concept someway (not sure how) into Flutter's dependency resolution?