Rob Holt

Sorry, meant to get back sooner. The problem [here](https://github.com/PowerShell/vscode-powershell/issues/1440#issuecomment-477566091) is that the tests use a hosted PowerShell instance (since xUnit doesn't play well with PowerShell), so it depends on some...

This is likely a duplicate of https://github.com/PowerShell/vscode-powershell/issues/261

Yes I think our desire here is to implement renaming only in the current scope, so not trying to infer any scope sharing. So if you were to rename `$foo`...

Oh I agree, but at the end of the day we can: 1. Give people nothing 1. Implement a safe, restrained feature 1. Make a dangerous decision that does invalid...

This should be possible by using PowerShell's API for getting PSMethod overload definitions. e.g. ```powershell [string]::Combine.OverloadDefinitions ```

> Also the OverloadDefinitions property is just an array of strings Wow

@SydneyhSmith going to reopen this one. Essentially, PSReadLine does parameter intellisense pretty well but it does something beyond PowerShell. This means it's possible, but we need to do extra work....

Thanks for looking into that @mattpwhite! Looks like further motivation for https://github.com/PowerShell/PowerShellEditorServices/issues/1295

Oh I just realised this isn't a completion bug, it's a completion *trigger* issue; it you press Ctrl+Space, you get the intellisense. We need some way of telling VSCode to...

So I think adding a configuration like this to PSScriptAnalyzer's settings file makes sense, and for that I'd ask you to open a feature request issue in the PSScriptAnalyzer repo....