-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
Null safety #50
Comments
I have no problems moving to null safety, I just don't follow dart news closely and missed this. I can look into it this weekend, you are also welcome to make a PR if you get to it sooner. Also need to read up on the changes and setup my versions appropriately |
No worries - the |
package:crypto should have null safety enabled soon, see dart-lang/crypto#107 |
Looks like this is mostly done. Is there a reason the null safe branch hasn't been merged into master? Can we merge and publish? |
I'll open another PR to remove the dependency overrides then. As soon as that's through I think this package is ready. |
Oh wait, it looks |
cc @natebosch is looking at publishing a null safe version of crypto. Tracking issue: dart-lang/crypto#105 |
Ya, once crypto gets a nullsafety package on pub, I'll push out a nullsafety version of this. Just been waiting on dependencies. |
I accidentally migrated this package for myself because I didn't see the existing branch. I noticed that it is very easy to remove the
|
That is a good point. I think I can make the change to the nullsafety branch in a way that will keep nullsafety. |
Ok, removed dependency to convert, but the crypto dependency is pretty necessary, and until they release a nullsafety version, i cant publish to pub. (I tried it with dart-otp and it blocked the push). Until then it will stay on the nullsafety branch, but it is ready to merge to master as soon as that nullsafety crypto version is released. |
Ugh, still a no go. It seems because I use Crypto as a direct dependency, the Override applies to it also for some reason and won't let me publish
It is still related to |
Crypto has been published: https://pub.dev/packages/crypto/versions/3.0.0-nullsafety.0 |
I am aware, but if you look at the last 2 references, and hte post before them. There are other issues that need to be solved before I can publish. I am currently blocked from publishing until those changes are made. I have those tickets open tracking it. |
FWIW I think we can do the following to publish an update now:
To my best knowledge, that shouldn't break anything since our |
I'll think about that. I feel passing the buck down to downstream users would just open me up to a whole bunch of new issues being opened about how it's breaking builds. Also that does seem super fragile. Honestly I think dart devs should have finished porting all of their stuff before telling everyone else to do it. I see so many open issues about nullsafety versions and lots of blockers on dart team owned libraries not being ported. I might still do your suggestion. Let me think on it. |
After getting the same instructions from a Dart dev. I have removed test/dev_dependencies long enough to push, and pushed up the change. 3.0.0-nullsafety.0 is published. I will now close this ticket. Please open a new one if there are any other problems |
Thank you! |
Dart 1.12 is in beta and supports null safety - time to migrate packages. Can this package be migrated? I'm happy to open a PR for that.
The text was updated successfully, but these errors were encountered: