Closed jonathanpeppers closed 6 days ago
As a further future step, we should also multitarget to net9.0
(even if only locally) and fix those warnings, as the netstandard2.0
BCL isn't fully annotated with nullable annotations.
As a further future step, we should also multitarget to
net9.0
(even if only locally) and fix those warnings, as thenetstandard2.0
BCL isn't fully annotated with nullable annotations.
maybe upgrading to netstandard2.1 might be better?
The two test failures we can ignore:
Introduces the setting to
Xamarin.Android.Build.Tasks.csproj
:Then I fixed the existing warnings. Down the road this will make it easier to adopt
#enable nullable
, and eventuallyNullable=enable
the entire project. Trying to do that now results in 1,000+ warnings...Most of these are types that could easily be null, and they weren't marked as nullable with
?
. Luckily, the code appears to be checking for null in these places already.