github DotNetAnalyzers/StyleCopAnalyzers 1.3.109-beta

pre-release2 hours ago

A follow-up to 1.3.98-beta. It eases several layout rules that were too strict, including the new SA1143, adds a rule for generic cref syntax, and improves code fixes. Thanks to @bgrainger for the SA1143 fix, their first contribution.

Highlights

  • Fewer false positives. SA1143 allows branches that continue onto more lines. SA1118 allows multi-line string and switch-expression arguments. SA1500 and SA1513 allow an operator such as ?? right after a switch expression's closing brace. (#4336, #4331, #4333, #4334)
  • New rule SA1654 reports escaped generic brackets in XML documentation crefs, for example List<T>, and its code fix converts them to List{T}. (#4328)
  • Code fixes. SA1115 has a new code fix, SA1003's Fix All edits each document in one pass, and the SA1501 fix no longer crashes at the end of a file. (#4326, #4329, #4327)

Behavior changes worth knowing about

  • New rule on by default: SA1654 (use {T} rather than escaped <T> in cref attributes) is enabled as a warning. (#4328)
  • Fewer diagnostics from SA1143, SA1118, SA1500 and SA1513 in the cases described above. (#4336, #4331, #4333, #4334)

All changes

Enhancements

Fixes

  • Allow multiline conditional expressions by @bgrainger in #4336
  • SA1118: Allow multiline string arguments by @AArnott in #4331
  • SA1118: Allow multiline switch expressions with single-line headers by @AArnott in #4333
  • SA1500/SA1513: Allow continuations after switch expression closing braces by @AArnott in #4334
  • SA1501: Handle code fixes at end of file by @AArnott in #4327

New Contributors

Full Changelog: 1.3.98-beta...1.3.109-beta

Don't miss a new StyleCopAnalyzers release

NewReleases is sending notifications on new releases.