MartinGC94
MartinGC94
> it seems that the automatic variables which are created by the use of `[CmdletBinding()]` for TabExpansion2 should also be removed from completion, yes? You mean variables like `$PSCmdlet`? I...
I think you misunderstand the request. The type inference I'm talking about is used by the tab completion to figure out the type of expressions so it can give relevant...
That's just one of the parameters from the tabexpansion2 function, if you change the name in the example above to "tokens2" or something then it won't work.
I have a PR to fix that: https://github.com/PowerShell/PowerShell/pull/18763 but this issue is about the type inference for `[ref]` not the tabexpansion2 scope issue.
@ImportTaste How are you loading your functions to prevent PSScriptRoot from getting a value? The only method I can think of is manually pasting the function definition into the console....
@theJasonHelmick Any update from the working group?
Do you have any endpoint protection agents like SentinelOne installed? Some of them will inject themselves into the process which will also trigger this message.
@SteveL-MSFT @iSazonov If you decide to go that route I think a better verb choice would be `Complete`, as in `Complete-Progress`.
> with a runtime check in set_Activity when the Completed parameter is used and produce an error if Completed is not used and activity is not provided I don't understand...
I've applied the WG suggestions with a slight modification: I added the runtime check to ProcessRecord instead of the setter for Activity because parameters can be bound in any order...