Fixed
Status Update
Comments
tn...@google.com <tn...@google.com> #2
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
ju...@google.com <ju...@google.com> #3
Almost 2 months later and this is still broken
tn...@google.com <tn...@google.com> #4
Since there is no progression, I wanted to share our quick-fix for the issue.
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
an...@google.com <an...@google.com> #6
What is the status of this item?
Description
The
UnknownNullness
lint check only looks at nullness annotations on the item being inspected, which means that the following definitions using a type-use@Nullable
trigger the check:Since the annotations here are applied directly to the type of the item, they have effectively the same meaning as annotating the item itself with a non-type-use
@Nullable
.The check should also look at the annotations present on the
PsiType
and not report a lint violation if there is a nullness annotation.I see that the issue is being reported here . I can contribute a fix if someone from the lint team will review it.