-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Fix first batch of warnings in the Android embedding #30807
Conversation
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for all these tiny fixes!
Tests seem to be stuck, this may benefit from a rebase and a test kick |
This pull request is not suitable for automatic merging in its current state.
|
test-exempt: code refactor with no semantic change thanks for doing this!! |
The test failures are definitely related to the updates in this patch. |
…lutter#30807)" (flutter#31277)" This reverts commit ea83865.
Fixes ~400 warnings. Almost all the warnings are about specifying nullability annotations
for better compatibility with Kotlin.
https://developer.android.com/kotlin/interop#nullability_annotations
There are 986 warnings left.