|
1 | | -# The PowerShell Script Analyzer will generate a warning |
2 | | -# diagnostic record for this file due to a bug - |
3 | | -# https://github.com/PowerShell/PSScriptAnalyzer/issues/472 |
| 1 | +# Use the PowerShell extension setting `powershell.scriptAnalysis.settingsPath` to get the current workspace |
| 2 | +# to use this PSScriptAnalyzerSettings.psd1 file to configure code analysis in Visual Studio Code. |
| 3 | +# This setting is configured in the workspace's `.vscode\settings.json`. |
| 4 | +# |
| 5 | +# For more information on PSScriptAnalyzer settings see: |
| 6 | +# https://github.com/PowerShell/PSScriptAnalyzer/blob/master/README.md#settings-support-in-scriptanalyzer |
| 7 | +# |
| 8 | +# You can see the predefined PSScriptAnalyzer settings here: |
| 9 | +# https://github.com/PowerShell/PSScriptAnalyzer/tree/master/Engine/Settings |
4 | 10 | @{ |
5 | 11 | # Only diagnostic records of the specified severity will be generated. |
6 | 12 | # Uncomment the following line if you only want Errors and Warnings but |
7 | 13 | # not Information diagnostic records. |
8 | 14 | #Severity = @('Error','Warning') |
9 | 15 |
|
10 | 16 | # Analyze **only** the following rules. Use IncludeRules when you want |
11 | | - # to invoke only a small subset of the defualt rules. |
| 17 | + # to invoke only a small subset of the default rules. |
12 | 18 | IncludeRules = @('PSAvoidDefaultValueSwitchParameter', |
13 | 19 | 'PSMisleadingBacktick', |
14 | 20 | 'PSMissingModuleManifestField', |
|
25 | 31 | # Note: if a rule is in both IncludeRules and ExcludeRules, the rule |
26 | 32 | # will be excluded. |
27 | 33 | #ExcludeRules = @('PSAvoidUsingWriteHost') |
| 34 | + |
| 35 | + # You can use rule configuration to configure rules that support it: |
| 36 | + #Rules = @{ |
| 37 | + # PSAvoidUsingCmdletAliases = @{ |
| 38 | + # Whitelist = @("cd") |
| 39 | + # } |
| 40 | + #} |
28 | 41 | } |
0 commit comments