bosskmk / pluto_grid

PlutoGrid is a dataGrid for flutter that can be controlled by the keyboard on desktop and web. Of course, it works well on Android and IOS.
https://pluto.weblaze.dev
MIT License
636 stars 290 forks source link

[Problem] Conflict with "intl 1.9.0" #996

Closed softplaceio closed 3 months ago

softplaceio commented 6 months ago

Hello,

I can't update "intel: ^1.9.0" because plot_grid needs "intl: ^1.8.0". How can I resolve my situation?

Resolving dependencies...
Because pluto_grid 7.0.2 depends on intl ^0.18.0 and no versions of pluto_grid match >7.0.2 <8.0.0, pluto_grid ^7.0.2 requires intl ^0.18.0.
So, because budget_generator depends on both intl ^0.19.0 and pluto_grid ^7.0.2, version solving failed.

You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on intl: flutter pub add intl:^0.18.1
exit code 1
NNanosoft commented 5 months ago

Hello dears, I am facing the same issue. The dependencies need to be updated. (for intl 0.9.0) I have seen that there have been no commits since 8 months ago on git repository, does it mean that the project was abandoned by developers?

doonfrs commented 5 months ago

@NNanosoft https://pub.dev/packages/pluto_grid_plus

NNanosoft commented 5 months ago

thank you @doonfrs
but is there any official communication from the project team saying that the original project is not maintained anymore? @bosskmk could you please give us any feedback?

reyadd-az commented 5 months ago

I faced a similar issue, pluto_grid: ^7.0.2 required intl: ^0.18.0, but had few other packages that require intl: ^0.17.0. and the project was not building because the dependencies could not be resolved.

I solved it as follows: I copied the folder (pluto_grid-7.0.2) from the cache Pub\Cache\hosted\pub.dev\pluto_grid-7.0.2 to a local folder, then changed the pubspec entry to intl: ^0.17.0. saved and ran pub get, then moved pluto_grid-7.0.2 back to cache. now my project builds with no conflicts. I know the approach my not be the best but it was my last resort. at lease I resolved the conflict.

github-actions[bot] commented 4 months ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 3 months ago

This issue was closed because it has been inactive for 14 days since being marked as stale.