Can I still migrate current project to support null-safety while some of the dependencies not support it yet?
Question
It would take too long to wait until all dependencies to support the null-safety. So I am thinking not to wait for them. I wonder if I can do or should do that.
1 answers
solution1
0 2020-11-26 05:32:30
First requirement in https://dart.dev/null-safety/migration-guide (a Google-provided document, and they should know):
- Wait for the packages that you depend on to migrate.
So, wait.
You can help speed it up by helping them migrate (post an issue first, or look for any existing issue to watch). Pull requests welcome!
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.
Related Question
Null safety migration error: package has unmigrated dependencies. But all my dependencies declare support for null-safety
Update flutter project to stable null-safety
Flutter mockito unit test error after migrate null-safety
Cannot build dart project due to custom dependencies doesn't support sound null safety
The current Dart SDK version does not satisfy null-safety dependences
Dart Null-Safety - Range Error when executing dart migrate to upgrade to new null safety
Flutter 2.0 following dependencies don't support null safety
Cannot run with sound null safety, because the following dependencies don't support null safety
Error: Cannot run with sound null safety, because the following dependencies don't support null safety; in flutter
Cannot run with sound null safety because dependencies doesnot support null safety
Related Tags