-
Notifications
You must be signed in to change notification settings - Fork 236
FEATURE REQUEST: Intellisense for PSScriptAnalyzerSettings.psd1 #973
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@travis-c-lagrone see PowerShell/PSScriptAnalyzer#675 (comment) for your second request |
Seems like "schema for PSD1" files is a request that should be made on the PowerShell project. Either that, or request an alternate format for settings that does support schema - like JSON. For the PSSA settings file, I don't see a compelling reason to use PSD1 over JSON. |
Agreed |
@rkeithhill PowerShell #4016 would address "schema for PSD1" feature request, but it hasn't seen any activity since 2017. I've posted a question about progress, so we'll see what the answer is (if any). |
We're working on a few other things at the moment. The easier thing to do might be to add JSON support in PSSA (I recently rewrote the PSD parsing for that and now would be a good time to add such support). I'd recommend opening an issue there |
@rjmholt I have opened PSScriptAnalyzer #1254. |
Closed as mis-scoped duplicate of PSScriptAnalyzer #1254 |
FEATURE REQUEST: Intellisense for PSScriptAnalyzerSettings.psd1
Provide intellisense (suggestions and rule information) for any PSScriptAnalyzerSettings.psd1 file, wherein the intellisense is based on the expected format of PSSA files and the runtime value of
PSScriptAnalyzer\Get-ScriptAnalyzerRule
.Ideally, there would also be an option to configure one or more custom rule paths, but that might constitute a separate feature request on account of editor configuration differences.
The text was updated successfully, but these errors were encountered: