René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"ScriptAnalyzer is missing a lot of warnings","articleBody":"### Prerequisites\n\n- [x] I have written a descriptive issue title.\n- [x] I have searched all [_open and closed_ issues](https://github.com/PowerShell/PowerShellEditorServices/issues?q=is%3Aissue) to ensure it has not already been reported.\n- [x] I have read the [troubleshooting](https://github.com/PowerShell/vscode-powershell/blob/main/docs/troubleshooting.md) guide.\n- [x] I am sure this issue is with _PowerShell Editor Services itself_ and does not reproduce in a standalone [PowerShell](https://github.com/PowerShell/PowerShell/issues/new/choose) instance, and is not an issue with my editor.\n- [x] I have verified that I am using the latest version of PowerShell Editor Services.\n- [x] If this is a security issue, I have read the [security issue reporting guidance](https://github.com/PowerShell/vscode-powershell/blob/main/SECURITY.md).\n\n### Summary\n\nI've been using PSScriptAnalyzer (1.25.0) from the PowerShell command line on an individual file like:\n`Invoke-ScriptAnalyzer .\\foo.ps1`\n\nI'm getting warnings for rules: `PSAvoidShouldContinueWithoutForce`, `PSAvoidUsingInvokeExpression`, `PSReviewUnusedParameter`, `PSShouldProcess` and `PSUseSingularNouns`\n\nNow, I've been running PowerShellEditorServices LSP (latest version) in my editor on that same file but I'm not getting any of these warnings reported. And yes the LSP is working because it reported other types of errors/warnings normally.\n\nMy question is, is it possible to modify the default settings or rules included? Or is it a bug somewhere?\n\n### PowerShell Version\n\n```console\nC:\\Users\\grolongo\u003e $PSVersionTable\n\nName                           Value\n----                           -----\nPSVersion                      7.5.5\nPSEdition                      Core\nGitCommitId                    7.5.5\nOS                             Microsoft Windows 10.0.22631\nPlatform                       Win32NT\nPSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}\nPSRemotingProtocolVersion      2.3\nSerializationVersion           1.1.0.1\nWSManStackVersion              3.0\n```\n\n### Editor Version\n\n```console\nEmacs version: 30.2 (latest stable)\n\nLSP client setup is really simple:\n(use-package powershell :ensure t :demand t)\n\nthen to install the LSP server:\nM-x powershell-install-langserver\n\nEglot connects successfully.\n```\n\n### PowerShell Editor Services Version\n\n```console\nModuleVersion = '4.5.0'\n```\n\n### Steps to Reproduce\n\n1. create a ps1 file and write a simple function with a plural noun like `Install-Programs`\n2. run PSScriptAnalyzer: `Invoke-ScriptAnalyzer .\\foo.ps1` -\u003e `PSUseSingularNouns` warning reported\n3. open the same file in your editor with LSP on -\u003e no warning reported\n\n### Visuals\n\n_No response_\n\n### Logs\n\n_No response_","author":{"url":"https://github.com/grolongo","@type":"Person","name":"grolongo"},"datePublished":"2026-04-17T18:38:09.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/2280/PowerShellEditorServices/issues/2280"}