-
Notifications
You must be signed in to change notification settings - Fork 164
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
How to work with nullsafety (NNBD) #298
Comments
This package will have a released null safety version before the end of December. Following that, the NULL_SAFETY_README you mention gives more information. |
Thanks! Looking forward to it :) |
mockito 5.0.0-nullsafety.0 has been published. |
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is no
-nullsaftey.0
release but I saw that there is aNULL_SAFETY_README.md
document, so I assumed that some kind of null safety support exists. When I try however to add the latest version as a dependency, I get plenty of issues (for example:mockito
depends onlogging ^0.11.2
instead oflogging ^1.0.0-nullsafety.0
, or that I can't import the library because ofimport_of_legacy_library_into_null_safe
).Please state the plans and an approximate timeline of upgrading this library to null safety and how users of this library are supposed to proceed.
This package is used in all of my libraries so I'm stuck migrating any library until I know how I'm supposed to handle
mockito
.The text was updated successfully, but these errors were encountered: