SublimeLinter-contrib-PSScriptAnalyzer
Sublime Text Linter for PowerShell Core
Details
Installs
- Total 588
- Win 482
- Mac 63
- Linux 43
Jul 27 | Jul 26 | Jul 25 | Jul 24 | Jul 23 | Jul 22 | Jul 21 | Jul 20 | Jul 19 | Jul 18 | Jul 17 | Jul 16 | Jul 15 | Jul 14 | Jul 13 | Jul 12 | Jul 11 | Jul 10 | Jul 9 | Jul 8 | Jul 7 | Jul 6 | Jul 5 | Jul 4 | Jul 3 | Jul 2 | Jul 1 | Jun 30 | Jun 29 | Jun 28 | Jun 27 | Jun 26 | Jun 25 | Jun 24 | Jun 23 | Jun 22 | Jun 21 | Jun 20 | Jun 19 | Jun 18 | Jun 17 | Jun 16 | Jun 15 | Jun 14 | Jun 13 | Jun 12 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 |
Mac | 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 | 0 |
Linux | 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 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 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.