[v0.4.0] collection version conflict between the v0.4.0 and flutter_test about http-mock-adapter HOT 9 CLOSED

@LukaGiorgadze we explicitly tried to avoid this version bump of collection in the Dio upgrade branch

from http-mock-adapter.

Meanwhile I can use 'dependency_overrides' to my troublesome projects' pubspec.yaml.

dependency_overrides:
collection: "1.17.1"

from http-mock-adapter.

@chunghha Could you try to update test to the latest version in your pubspec?

from http-mock-adapter.

@LukaGiorgadze I believe typically projects have this set with "flutter_test" as the below which uses collection.

flutter_test:
sdk: flutter

That means collection version from sdk should be set with http_mock_adapter.

I set my projects with minimum sdk version 2.19.0 so collection 1.17.0 matches with. If someone else wants a. lower minimum sdk version then probably setting the collection version to 1.15.0 is the safe bet as @kuhnroyal pointed in the review of dio v5 PR.

https://pub.dev/packages/collection/changelog

from http-mock-adapter.

Yes the problem is that flutter enforces a certain collection version. Stable (Flutter 3.7) is on collection: 1.16.0 but if you want some form of backward compatibility then the library should target 1.15.0.

from http-mock-adapter.

@chunghha @kuhnroyal
According to Flutter's official Github, it seems that they have an updated version of the collection (1.7.1).
https://github.com/flutter/flutter/blob/master/packages/flutter_test/pubspec.yaml#L35

Could you try flutter update-packages ?

I'm okay to revert it back, but I want to make sure that you have guys the latest versions of flutter + packages that depend on the collection.

from http-mock-adapter.

I concur with what @kuhnroyal wrote about the backward compatibility.

I have the latest Flutter stable sdk version 3.7.3 installed, so with flutter_test from the sdk version, collection 1.7.0 is installed for my project. Then I got to override the version to 1.7.1 in the pubspec.yaml in order for me to install http_mock_adapter 0.4.0 because it requires the 1.7.1.

from http-mock-adapter.

I guess downgrading collection to 1.16.0 in http_mock_adapter can solve that problem so there won't be any incompatibility. How does it sound? @chunghha @kuhnroyal

from http-mock-adapter.

Take a look at this PR #142

from http-mock-adapter.