Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not use .Where or .WhereNotNull followed by an argumentless .(Single|First|Last)(OrDefault)? #44

Open
amanda-mitchell opened this issue Feb 5, 2019 · 0 comments
Labels
new analyzer Suggestion for a new analyzer to add

Comments

@amanda-mitchell
Copy link
Contributor

amanda-mitchell commented Feb 5, 2019

I'm told that ReSharper does find this one (see #36), although it is unaware of WhereNotNull.

Caveat: we may not wish to flag instances in which WhereNotNull is called with a Nullable<T> type parameter, since this also changes the return type of the expression.

@amanda-mitchell amanda-mitchell added the new analyzer Suggestion for a new analyzer to add label Feb 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new analyzer Suggestion for a new analyzer to add
Development

No branches or pull requests

1 participant