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

Fixed issue in CodeFixVerifier #1203

Merged
merged 1 commit into from
Aug 14, 2015

Conversation

vweijsters
Copy link
Contributor

Fixed an issue where the incremental code fix verifier would terminate early because the new diagnostics set and the old diagnostics set only differed by location.

Also corrected the failing tests in SA1501UnitTests as a result of this bug fix.

@@ -746,7 +717,7 @@ public void Bar(int i)

await this.VerifyCSharpDiagnosticAsync(testCode, expected, CancellationToken.None).ConfigureAwait(false);
////await this.VerifyCSharpDiagnosticAsync(fixedCode, EmptyDiagnosticResults, CancellationToken.None).ConfigureAwait(false);
await this.VerifyCSharpFixAsync(testCode, fixedCode, batchFixedCode, cancellationToken: CancellationToken.None).ConfigureAwait(false);
await this.VerifyCSharpFixAsync(testCode, fixedCode, fixedCode, cancellationToken: CancellationToken.None).ConfigureAwait(false);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 You can just remove the third parameter. It assumes the batch fixer output matches the incremental fixer if you don't specify something for batchNewSource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants