I've seen that there is a null-safety
branch, but it doesn't seem to be maintained.
It would be great if you could state your intent on when you'll be migrating to null-safety.
Maybe it makes sense to pin this issue.
Hi @enyo 馃憢
Thanks for opening an issue!
The null-safety branch is open to test null safety and report feedback to the Dart team.
As far as I know, the dart team does not recommend publishing third party packages with null safety support since it is still under development. My intention is to update and publish these changes when nnbd lands in stable.
Hope that helps 馃憤
Thanks for the swift response. Ok that makes sense. I've seen plenty of libraries releasing versions like 7.0.0-nullsafety.1
. Is that also no recommended?
And: is the null-safety
branch usable? I think that, for example, the flutter_bloc
package isn't ported yet?
As far as I know it isn鈥檛 recommend to publish packages as nnbd isn鈥檛 considered production ready at this stage.
Flutter experimentation with technical preview 2: This is today. Because we鈥檝e successfully migrated the core Flutter framework to null safety, you鈥檙e able to try null safety to learn the new language feature and experiment with a small Flutter sample. If you鈥檙e a package author, you may also be able to do a trial migration, if you have a small dependency set that鈥檚 already been migrated by us. You need to pass an experiment flag, shouldn鈥檛 use it in production, and shouldn鈥檛 publish any migrated packages.
https://link.medium.com/1iT0ZIREpbb
I plan to migrate flutter_bloc in the near future but the initial push was for pure dart packages and in order to migrate flutter_bloc, provider would have to be migrated first.
@felangel hey since Null Safety is in beta, it is time to update Bloc library to support null safety. Are there any timelines on this? Thanks!
@Yegorisa yes I plan to publish a null-safety version within the next day or two 馃憤
Most helpful comment
@Yegorisa yes I plan to publish a null-safety version within the next day or two 馃憤