SublimeLinter-contrib-PSScriptAnalyzer
Sublime Text Linter for PowerShell Core
Details
Installs
- Total 617
- Win 507
- Mac 67
- Linux 43
Oct 24 | Oct 23 | Oct 22 | Oct 21 | Oct 20 | Oct 19 | Oct 18 | Oct 17 | Oct 16 | Oct 15 | Oct 14 | Oct 13 | Oct 12 | Oct 11 | Oct 10 | Oct 9 | Oct 8 | Oct 7 | Oct 6 | Oct 5 | Oct 4 | Oct 3 | Oct 2 | Oct 1 | Sep 30 | Sep 29 | Sep 28 | Sep 27 | Sep 26 | Sep 25 | Sep 24 | Sep 23 | Sep 22 | Sep 21 | Sep 20 | Sep 19 | Sep 18 | Sep 17 | Sep 16 | Sep 15 | Sep 14 | Sep 13 | Sep 12 | Sep 11 | Sep 10 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | 1 | 1 | 0 | 2 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 |
Mac | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Linux | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Readme
- Source
- raw.githubusercontent.com
SublimeLinter-contrib-PSScriptAnalyzer
This linter plugin for SublimeLinter provides an interface to PowerShell's PSScriptAnalyzer module. It will be used with files that have the “PowerShell” syntax.
Installation
SublimeLinter must be installed in order to use this plugin.
Please use Package Control to install the linter plugin.
Before installing this plugin, you must ensure that:
pwsh
is installed on your system (PowerShell Core).- Module PSScriptAnalyzer is installed. If not, install it from PowerShell:
Install-Module -Name PSScriptAnalyzer
In order for pwsh
to be executed by SublimeLinter, you must ensure that its path is available to SublimeLinter. The docs cover troubleshooting PATH configuration.
PSScriptAnalyzer settings
If a file named PSScriptAnalyzerSettings.psd1
exists in the user's home directory it's used as PSScriptAnalyzer's settings file when calling Invoke-ScriptAnalyzer
cmdlet. Please refer to PSScriptAnalyzer for details.
Example content of a settings file:
@{
# Select which diagnostic records to show.
# Valid values are: ParseError, Error, Warning, Information
Severity = @('ParseError', 'Error', 'Warning')
ExcludeRules = @(
'PSUseApprovedVerbs'
)
IncludeDefaultRules = $true
}
Path/name of the PSScriptAnalyzer's settings can be customized:
"linters": {
...
"psscriptanalyzer": {
// full path
"settings": "D:\\Scripts\\CustomSettings.psd1"
// environment variables will be expanded
"settings": "%SCRIPTS_DIR%\\CustomSettings.psd1"
// or built-in preset name (beware that linting fails if the name is not a valid preset name)
"settings": "PSGallery"
// default - remove or set to null
"settings": null
}
General Settings
- SublimeLinter settings: http://sublimelinter.readthedocs.org/en/latest/settings.html
- Linter settings: http://sublimelinter.readthedocs.org/en/latest/linter_settings.html
TODO
- Handle the case when a given preset name is not a valid PSScriptAnalyzer preset. Now it just fails to lint.