Migrate null safety #364
Closed
Migrate null safety #364
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hienlh
force-pushed
the
migrate-null-safety
branch
from
9a02dd4 to
e84b2bc
Compare
Jeasmine
reviewed
Mar 25, 2021
There was a problem hiding this comment.
Hey! Thank you for your contribution. We are working on supporting null safety under the major release branch. But since this is for master and for backporting. Can you follow the same changes as #370 to have the same code styling and null safety practices?
Sure, no problem |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Migrated the project to Flutter 2.0 and made some adjustments to support
sound null safety.This change is