We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Rosylnator Analyzers 4.12.7:
Steps to Reproduce: Create a custom exception, use the custom exception in a try/catch, where you don't use the exception.
Here is an example project: https://github.com/merlinschumacher/Roslyn-RCS1140-Issue
With 4.12.6 the issue isn't present.
Actual Behavior: This triggers an argument null exception. Independent of the presence of an XML comment for the exception:
try { Method2(); } catch { throw new MyCustomException("MyCustomException"); }
This works (passing the caught exception is not necessary):
try { Method2(); } catch (Exception ex) { throw new MyCustomException("MyCustomException"); }
Expected Behavior: To create an analyzer message notifying me of the possibly missing XML comment.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Rosylnator Analyzers 4.12.7:
Steps to Reproduce:
Create a custom exception, use the custom exception in a try/catch, where you don't use the exception.
Here is an example project:
https://github.com/merlinschumacher/Roslyn-RCS1140-Issue
With 4.12.6 the issue isn't present.
Actual Behavior:
This triggers an argument null exception. Independent of the presence of an XML comment for the exception:
This works (passing the caught exception is not necessary):
Expected Behavior:
To create an analyzer message notifying me of the possibly missing XML comment.
The text was updated successfully, but these errors were encountered: