ulrichb/ImplicitNullability

Issues

• Incorrect behavior for Implicit nullability v4.9.0.13340193

  #28 opened 5 years ago by zyrianovdv
  1

• Implicit nullability for static readonly fields and properties

  #27 opened 6 years ago by tom-englert
  3

• Selectively reverting to Resharper default nullability?

  #15 opened 6 years ago by jklw
  1

• ReSharper integration

  #25 opened 6 years ago by NN---
  1

• Support R# 2019.1

  #26 opened 6 years ago by tom-englert
  3

• Integration into ReSharper CLT?

  #19 opened 7 years ago by iluuu1994
  4

• Syntax Highlighting is Broken

  #24 opened 6 years ago by jrharnden
  3

• Rider plugin doesn't show errors when expression is more complex

  #23 opened 7 years ago by safesparrow
  2

• Support for "Nullable reference types"

  #21 opened 7 years ago by rollsch
  1

• support something that achieves the following Func<[NotNull]string>

  #22 opened 7 years ago by rollsch
  1

• Update for Resharper 2018.1

  #20 opened 7 years ago by FutureTD
  2

• Support for R# 2016.1

  #2 opened 9 years ago by drewnoakes
  11

• ReSharper 2017.1

  #12 opened 8 years ago by matkoch
  4

• Cannot install plugin in Rider2017.3

  #16 opened 7 years ago by DenisPimenov
  3

• Bug for properties nullability

  #18 opened 7 years ago by zyrianovdv
  2

• Assume NotNull for Inherited (Implemented) Members

  #17 opened 7 years ago by Mike-E-angelo
  6

• Handle Nullable<> in generic Methods

  #9 opened 7 years ago by pothos-dev
  2

• Difference in behavior between explicit and implicit [NotNull]

  #13 opened 7 years ago by cmeeren
  3

• Implicit NotNull for properties

  #7 opened 7 years ago by srollinet
  8

• Skip detection of XAML members or detect call to InitializeComponent

  #11 opened 8 years ago by cmeeren
  12

• AssemblyMetadata in .NET < 4.5?

  #14 opened 8 years ago by cmeeren
  3

• Field nullability is checking backing fields for properties

  #10 opened 8 years ago by johnendev
  1

• "void" in "async void" detected as implicit/explicit NotNull

  #8 opened 8 years ago by cmeeren
  2

• Use assembly/class level attribute to enable this with some level of granularity

  #3 opened 9 years ago by drewnoakes
  6

• ImplicitNotNullConflictInHierarchy requires code duplication

  #1 opened 9 years ago by kwesolowski
  2