The tuple data structure is too simple and there is no reason to use 3rd party packages. You can always create your own class with 2 fields and do whatever you want. The 3rd party packages cause dependency conflicts. Sometimes it can be very nasty. Here is the problem which I have encountered.
Because no versions of signalr_core match >1.1.1 <2.0.0 and signalr_core 1.1.1 depends on tuple ^2.0.0, signalr_core ^1.1.1 requires tuple ^2.0.0.
And because no versions of tuple match >2.0.0 <3.0.0 and tuple 2.0.0 depends on quiver ^3.0.0, signalr_core ^1.1.1 requires quiver ^3.0.0.
And because flutter_layout_grid 0.10.5 depends on quiver ^2.0.0 and no versions of flutter_layout_grid match >0.10.5 <0.11.0, signalr_core ^1.1.1 is incompatible with flutter_layout_grid ^0.10.5.
And because flutter_html 1.3.0 depends on flutter_layout_grid ^0.10.5 and no versions of flutter_html match >1.3.0 <2.0.0, signalr_core ^1.1.1 is incompatible with flutter_html ^1.3.0.
So, because aura_mobile depends on both flutter_html ^1.3.0 and signalr_core ^1.1.1, version solving failed.
pub get failed (1; So, because aura_mobile depends on both flutter_html ^1.3.0 and signalr_core ^1.1.1, version solving failed.)
Please, stay away from 3rd party packages as much as you can and remove those which you can easily make yourself.
The tuple data structure is too simple and there is no reason to use 3rd party packages. You can always create your own class with 2 fields and do whatever you want. The 3rd party packages cause dependency conflicts. Sometimes it can be very nasty. Here is the problem which I have encountered.
Please, stay away from 3rd party packages as much as you can and remove those which you can easily make yourself.