Skip to content
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

Dependency incompatibility with flutter_map #64

Open
digitalentity opened this issue Aug 1, 2023 · 1 comment
Open

Dependency incompatibility with flutter_map #64

digitalentity opened this issue Aug 1, 2023 · 1 comment

Comments

@digitalentity
Copy link

As said in the title - it's not possible to use graphx and flutter_map in the same project due to dependency conflict:

Because graphx >=1.0.0-nullsafety.0 <1.0.1 depends on http ^0.13.1 and graphx <1.0.0-nullsafety.0 doesn't support null safety, graphx <1.0.1 requires http ^0.13.1.
And because graphx >=1.0.1 <1.0.4 depends on http ^0.13.3, graphx <1.0.4 requires http ^0.13.1.
And because graphx >=1.0.4 <1.0.5 depends on http ^0.13.4 and graphx >=1.0.5 depends on http ^0.13.5, every version of graphx requires http ^0.13.1.
Because no versions of flutter_map match >5.0.0 <6.0.0 and flutter_map 5.0.0 depends on http ^1.0.0, flutter_map ^5.0.0 requires http ^1.0.0.
Thus, flutter_map ^5.0.0 is incompatible with graphx.
So, because dartgcs depends on both flutter_map ^5.0.0 and graphx any, version solving failed.
@roipeker
Copy link
Owner

roipeker commented Aug 1, 2023

Did you try dependency_overrides?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants