Null-Safety migration

[RTrackerDev]

Do you plan migrate to null-safety? Next Dart(2.12) will be with stable and by default null-safety.

[mikolak]

Plan? Yes. When? I don't know. 🙂 Do you if that feature is backwards compatible?

Link for future reference: https://dart.dev/null-safety/migration-guide

[jdar]

While there's no need a formal roadmap... it would be useful to know the "bus factor" is on this project? Is this just one engineer (you) that is maintaining this?

[jlubeck]

Null safety is now on stable branch since yesterday, so it would be nice to have this so we can convert out projects to fully null safety. Thanks!

[DevNico]

Would be great to have a null safe version ASAP!

[okocsis]

Good news everyone:
I'm happy to announce that I've issued my very own PR to support Nullsafety.

I'd like you guys to have a look at my nullsafety branch:
#586
what are your thoughts? @mikolak
(as mentioned in the pr text, please do help me with the unnecessary and or still broken tests)

thanks!

[mikolak]

While there's no need a formal roadmap... it would be useful to know the "bus factor" is on this project? Is this just one engineer (you) that is maintaining this?

Temporarily I'm the only one on this. Had a bumpy transition and just today I've setup my machine to be able to do anything in the library. I'll try to address some of the issues next week.
There are talks with company willing to take over, but I don't know what's the state of things.

Good news everyone:
I'm happy to announce that I've issued my very own PR to support Nullsafety.

I'd like you guys to have a look at my nullsafety branch:
#586
what are your thoughts? @mikolak
(as mentioned in the pr text, please do help me with the unnecessary and or still broken tests)

thanks!

I'll take a look at this next week.

[okocsis]

I'll take a look at this next week.

@mikolak I've managed to fix the broken tests too.
(broken due to new nullsafe mockito API)
I think it should be fine now!
Thanks for reviewing mate!

@jlubeck @DevNico @jdar
Could you guys also have look at my branch and perhaps test if it behaves "well enough"?
Cheers,
Oliver

[mikolak]

FYI there's a release blocker (#591). As soon as I sort it out, I'll release 2.4.0 with null safety and API for checking if native client is allocated.

[Jakegillingham5]

FYI there's a release blocker (#591). As soon as I sort it out, I'll release 2.4.0 with null safety and API for checking if native client is allocated.

Is this far away from a release, just wanting an update? Planning to migrate my application to null safety but currently blocked by this at the moment.

[okocsis]

migrate my application to null safety but currently blocked by this at the moment.

@Jakegillingham5
You can still migrate your code to a so-called "unsound null safety". I mean I'm using a null safe version of FlutterBleLib maintaining it on my own fork https://github.com/privatdoktor/FlutterBleLib/tree/privatdoktor and even still my null safe migration isn't sound since there are still other dependencies not conforming to null safety. Perhaps time will fix these too.
I've also changed a couple of other features that needed fixing and enhancements, mostly on iOS side. I've more or less given up on waiting for Polidea for mering in my work. I might even rerelease the library to the public when it reaches a stable state.

[Jakegillingham5]

@okocsis
Awesome thanks so much for this, I actually made the call last week to just use your commit '1beac74' and bring my project up to date ['unsound null safety' - Flutter 2.2.1]. Will move to your fork now though as most of our users are on iOS so will benefit from any changes in that space, cheers mate.