Closed nischalkumar closed 3 years ago
This also fixes https://github.com/ofload/native_updater/issues/16
@nischalkumar thank you very much for your contribution. Super duper explanations here 🎉 🤗
In the future, try to add this in the commit message itself so anyone can read it without having to come back to the PR.
I'm very happy with your changes and will merge the PR.
This pr contains 3 commits:
Why are the changes done: Flutter 2.0 has introduced null safety, Now every new version of popular libraries(firebase, http, e.t.c.) recent releases only support null safety and now support for Flutter1.0 is getting thinner. Any flutter project has now to choose either to embrace completely null safety or stay with stale packages(missing out latest fixes and features). Having best of both world is now very tiresome. For more: understanding null safety
Now The projects who have migrated to null safety or started with null safety can not use native_updator as it has no null safety version. People like these( i recently migrated my project to null safety as I wanted to update firebase dependencies for which null safety is a must) have no choice other than moving out of native_updator.
With flutter 2.0 FlatButtons got deprecated in favour of TextButtons FlatButtons