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
In a previous commit, I introduced the `[ValidatedNotNull]` attribute to assure Code Analysis that the base methods in `TopicRepositoryBase` were performing parameter validation and, thus, could be assured that those parameters would not be `null`.
That was a necessary and useful addition. When I did that, however, I also added `[NotNull]`. There are cases where this makes sense. But it doesn't make sense here, since the value of the parameters is already marked as not nullable.
In fact, this causes newer versions of Roslyn's static flow analysis to identify this as a mismatch between these versions of the methods and the methods that `override` them in e.g. `SqlTopicRepository`.
This seems like a false positive to me, and I could even see that being a nuissance in other scenarios, but as it's the attribute isn't even needed here, we'll evaluate that issue if and when we come across a scenario where it really is a problem.
0 commit comments