Disable SA1000: Keywords should be spaced correctly #14292
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
assigned
Contributor
Author
|
@iSazonov Please merge ASAP. |
Contributor
Author
Originally posted by @xtqqczze in #13973 (comment) |
Contributor
Author
|
@iSazonov @adityapatwardhan SA1000 is now causing failures in CI: https://dev.azure.com/powershell/PowerShell/_build/results?buildId=69096&view=results |
Contributor
Author
|
Closed in favour of #14297. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Disable SA1000 analyzer that was enabled in #13973 because the StyleCopAnalyzers version does not recognise target-typed new expressions.