Enable SA1000: Keywords should be spaced correctly#13973
Enable SA1000: Keywords should be spaced correctly#13973iSazonov merged 1 commit intoPowerShell:masterfrom
Conversation
|
Still draft? |
|
This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days. |
|
@iSazonov Please review and merge. |
| @@ -113,7 +113,7 @@ private void SetResumeResponseHeaders() | |||
| private bool TryGetRangeHeader(out string rangeHeader) | |||
| { | |||
| var rangeHeaderSv = new StringValues(); | |||
There was a problem hiding this comment.
@xtqqczze For my education - does an analyzer recognize the "var" pattern to convert to
StringValues rangeHeaderSv = new();There was a problem hiding this comment.
I am not aware of such an analyzer, but one could use RCS1012 codefix first.
There was a problem hiding this comment.
So we should apply RCS1012 and then apply a fix to the new pattern?
|
I'm seeing warnings on the following pattern in live analysis, I'm surprised CI did not fail:
This issue was fixed in DotNetAnalyzers/StyleCopAnalyzers#3187, and is in the v1.2.0-beta.261 release. |
CI makes clean loading packages. So I guess if you see the warning you need clean your local package cache. |
CI is now failing |
Originally posted by @rjmholt in #9900 (comment) |
|
Between tests for this PR passing (12 days ago), we merged IDE0090 PRs, which conflicted as the version of StyleCopAnalyzers in use at the time did not support target-typed new expressions properly. We could reduce the likelihood of similar issues occurring again by running tests again between approval and merge. |
Ah, clear! We catch this again :-) |
|
🎉 Handy links: |
https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1000.md