Skip to content

Conversation

@sharwell
Copy link
Member

@sharwell sharwell commented Jan 6, 2026

Closes #3990

@codecov
Copy link

codecov bot commented Jan 6, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.49%. Comparing base (513ba0f) to head (9ebe0f2).

Additional details and impacted files
@@           Coverage Diff            @@
##           master    #4081    +/-   ##
========================================
  Coverage   97.48%   97.49%            
========================================
  Files        1026     1037    +11     
  Lines      119387   119600   +213     
  Branches     3476     3476            
========================================
+ Hits       116388   116602   +214     
  Misses       1986     1986            
+ Partials     1013     1012     -1     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.


DiagnosticResult[] expected =
{
Diagnostic(DiagnosticId).WithSpan(6, 22, 6, 30),
Copy link
Contributor

Choose a reason for hiding this comment

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

Any specific reason why markups are not used instead?

{
[Fact]
[WorkItem(3990, "https://github.com/DotNetAnalyzers/StyleCopAnalyzers/issues/3990")]
public async Task TestMixedDeconstructionDoesNotReportUnnecessaryParenthesesAsync()
Copy link
Contributor

Choose a reason for hiding this comment

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

Redundant because of the next test?

}
}";

await new CSharpTest()
Copy link
Contributor

Choose a reason for hiding this comment

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

Use VerifyCSharpFixAsync instead, as normal? I don't realize from reading this PR if there's a reason for doing it differently in this test.

}
}";

await new CSharpTest()
Copy link
Contributor

Choose a reason for hiding this comment

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

Same comment here

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Review impact of assignment and declaration in the same deconstruction on existing rules

2 participants