-
Notifications
You must be signed in to change notification settings - Fork 29
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
Issue635 partial classes #658
Conversation
This removed the need to check all methods for classes that only have read-only constants.
Do not check calls across compilation boundaries.
...alyzers/DisposeFieldsAndPropertiesInTearDown/DisposeFieldsAndPropertiesInTearDownAnalyzer.cs
Show resolved
Hide resolved
Take into account that get only properties and readonly fields can be assigned to in a constructor.
This to cope with cases where a field and an explicit property have the same name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks for all the work @manfred-brands
I'm facing the same exception being thrown. Any chance this fix could be rolled out into a 3.11 release? |
@alteredego I'll will see if I can get a release out this weekend - either a 3.11 or a 4.00 |
@mikkelbu - am I recommended to upgrade to 4.0+ and does this have a hard dependency on using NUnit 4? Thank you in advance! |
We will not backport the fix to 3.11, but the NUnit 4.X analyzers should work with both NUnit 3 and NUnt 4. |
I'll give 4.0.1 a go. Many thanks! |
Fixes #635
Fixes #659