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
Should GetNestedType be treated as a special case of GetType so that the existing #14 check is applied?
That would be cool because I'd totally prefer a refactoring from type.GetNestedType to type.Assembly.GetType("RepeatedTypeName+NestedTypeName, throwOnError: true) over avoiding NRE manually.
The text was updated successfully, but these errors were encountered:
jnm2
changed the title
Warn if GetNestedType is not checked for null or ovver refactoring to throw on error
Warn if GetNestedType is not checked for null or offer refactoring to throw on error
Nov 3, 2018
ErikWahlstrom
pushed a commit
to ErikWahlstrom/ReflectionAnalyzers
that referenced
this issue
Apr 5, 2019
Should
GetNestedType
be treated as a special case ofGetType
so that the existing #14 check is applied?That would be cool because I'd totally prefer a refactoring from
type.GetNestedType
totype.Assembly.GetType("RepeatedTypeName+NestedTypeName, throwOnError: true)
over avoiding NRE manually.The text was updated successfully, but these errors were encountered: