You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both of these imports lead to potential runtime problems if a null value is not guarded against.
When in a nullable context, use of AllowDefault = true on a non-nullable type should be flagged with a diagnostic. A codefix could also be added to change the type to be nullable.
The text was updated successfully, but these errors were encountered:
Strictly speaking, no import of a reference type is guaranteed to be non-null. Because you can export a property that returns null and that's perfectly legal.
But at least when AllowDefault = true it's much more likely to be null, so an analyzer that requires a nullable annotation at least for that case sounds like a good idea.
Both of these imports lead to potential runtime problems if a null value is not guarded against.
When in a
nullable
context, use ofAllowDefault = true
on a non-nullable type should be flagged with a diagnostic. A codefix could also be added to change the type to be nullable.The text was updated successfully, but these errors were encountered: