Support nullsafety #37
Comments
I'm sorry those are pre-release versions, and it would be premature to provide support for it. You may use dependency_overrides if you wish to work with those. |
yes, in understand but now need nullsafety with new version. Can you update? |
@humblerookie It seems like all the dependencies of this package have migrated to null safety and thus this package is ready to be migrated. Will you be doing this? |
@britannio I'm going to be busy this week, if you're comfortable contributing that would be great too. |
@humblerookie These packages depend are fastest version support null safety. Can you update? |
Do you just need the dependencies to be updated now or do you also require this package to itself be null safe? |
yes, update dependencies will support null safe. |
It's working with optimized_cached_image: ^2.0.1. Thanks |
Hi,
Can you update pack support nullsafety?
Because optimized_cached_image >=2.0.0-dev.1 depends on octo_image ^0.3.0 and cached_network_image 3.0.0-nullsafety depends on octo_image ^1.0.0-nullsafety, optimized_cached_image >=2.0.0-dev.1 is incompatible with cached_network_image 3.0.0-nullsafety.
And because no versions of cached_network_image match >3.0.0-nullsafety <4.0.0, optimized_cached_image >=2.0.0-dev.1 is incompatible with cached_network_image ^3.0.0-nullsafety.
So, because onedanang depends on both cached_network_image ^3.0.0-nullsafety and optimized_cached_image ^2.0.0-dev.2, version solving failed.
pub get failed (1; So, because onedanang depends on both cached_network_image ^3.0.0-nullsafety and optimized_cached_image ^2.0.0-dev.2, version solving failed.)
Thanks
The text was updated successfully, but these errors were encountered: