ulrichb / ImplicitNullability

Extends ReSharper's static nullability analysis by changing specific, configurable elements to be [NotNull] by default

ulrichb/ImplicitNullability Issues

Incorrect behavior for Implicit nullability v4.9.0.13340193
Closed 4 years ago1
Implicit nullability for static readonly fields and properties
Closed 5 years ago3
Selectively reverting to Resharper default nullability?
Closed 5 years ago1
ReSharper integration
Closed 5 years ago1
Support R# 2019.1
Closed 5 years ago3
Integration into ReSharper CLT?
Closed 6 years ago4
Syntax Highlighting is Broken
Closed 6 years ago3
Rider plugin doesn't show errors when expression is more complex
Closed 6 years ago2
Support for "Nullable reference types"
Closed 6 years ago1
support something that achieves the following Func<[NotNull]string>
Closed 6 years ago1
Update for Resharper 2018.1
Closed 6 years ago2
Support for R# 2016.1
Closed 8 years ago11
ReSharper 2017.1
Closed 7 years ago4
Cannot install plugin in Rider2017.3
Closed 6 years ago3
Bug for properties nullability
Closed 6 years ago2
Assume NotNull for Inherited (Implemented) Members
Closed 6 years ago6
Handle Nullable<> in generic Methods
Closed 6 years ago2
Difference in behavior between explicit and implicit [NotNull]
Closed 7 years ago3
Implicit NotNull for properties
Closed 7 years ago8
Skip detection of XAML members or detect call to InitializeComponent
Closed 7 years ago12
AssemblyMetadata in .NET < 4.5?
Closed 7 years ago3
Field nullability is checking backing fields for properties
Closed 7 years ago1
"void" in "async void" detected as implicit/explicit NotNull
Closed 7 years ago2
Use assembly/class level attribute to enable this with some level of granularity
Closed 8 years ago6
ImplicitNotNullConflictInHierarchy requires code duplication
Closed 8 years ago2