MartinGC94

It probably also makes sense to add support for `using namespace Alias = RealName` Special parsing rules were also made for `using command Alias = RealName` and `using module Alias...

>"using" is evaluated at parse time. I know, but what functionality would those 2 using directives have had? Namespace and Type is obvious, Command and Module are harder to guess.

Maybe I wasn't clear, but I meant that the `using module Alias = RealName` syntax was unimplemented and that I couldn't figure out what the original intent may have been....

What would happen if you splat the splat parameter? ``` $Params = @{ Path = "C:\" Splat = @{ LiteralPath = "C:\" } } gci @Params ```

My only 2 concerns are: 1: Normal functions/scripts don't get common parameters, so if I define a function like this: `function MyFunction ($Test){}` I won't be able to use this...

It's been 5 years. Has the platform gotten better so this can be added?

Yes. From what I understood of the issue mentioned earlier the LSP is getting the correct results, they just aren't shown in the VS code GUI because of the filter...

I don't think there's a setting for the command help we get when completing command names and I haven't heard anyone complain about that so I'm not sure if a...

I assume you are referring to this issue: https://github.com/PowerShell/PowerShellEditorServices/pull/2222 ? The related PR hasn't been merged yet: https://github.com/PowerShell/PowerShell/pull/25108 so the only tooltip we have today is the type and name...

As a workaround people can add this function to their `$profile` to filter out these file completion results: ``` function TabExpansion2 { [CmdletBinding(DefaultParameterSetName = 'ScriptInputSet')] [OutputType([System.Management.Automation.CommandCompletion])] Param( [Parameter(ParameterSetName = 'ScriptInputSet',...