Repository navigation
Clean up null assumptions for Gradle classes - #83443
Conversation
flutter-dashboard
Bot
added
the
tool
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat. If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
7235bd0 to
d28fffe
Compare
There was a problem hiding this comment.
Null outputDirectoryPath defaults to project.android.buildDirectory on line 197.
There was a problem hiding this comment.
It's possible to pass a nullable androidPackage here. Since it's just used for informational printing, default to "unknown".
There was a problem hiding this comment.
These are always passed in and assumed to be nonnull.
3 participants
I started migrating
project.dartand all its dependencies, and the diff was huge.Pull out the Gradle class cleanup parts that can be done without actually migrating to null safety.
Part of #71511