Null safety#18
Conversation
|
Hey, @jonmountjoy, I don't think this repo is accepting PRs. Why don't you upload this fork into pub.dev and mention the work of @j0j00 as inspiration? |
| @@ -1,5 +1,5 @@ | |||
| # Uncomment this line to define a global platform for your project | |||
| # platform :ios, '9.0' | |||
| platform :ios, '9.0' | |||
There was a problem hiding this comment.
Are all these iOS specific changes part of the null safety work?
I don't have an iOS device to test this on, so just curious if this is the best practice in latest Flutter dev or something.
|
Hi @jonmountjoy, Thanks for the PR. I'm pretty happy to make you a co-maintainer if you want as you seem pretty reputable, I think I might now be able to add new people as uploaders - which I don't think was available last time I checked a couple of months ago. Only thing missing from the PR is the appropriate changelog. |
|
Thanks @j0j00 - have now moved to a different library. There's a way, on https://pub.dev/ , to mark your package as deprecated/unsupported - perhaps you can do that? |
Adds null safety, bumps Podfile versions.
This is my best guess at what should happen, after following:
https://dart.dev/null-safety/migration-guide
My ultimate goal is to support https://github.com/fluttercommunity/flutter_sms getting to null safety, and this is a dependency.