When creating a scriptblock for Register-ArgumentCompleter Faster Result using Object imbedded Where and ForEach

Summary of the new feature/enhancement

$wordToComplete* filter should always be used at the end of the scriptblock, otherwise you will give unexpected result to the user.

Another suggetion is to use object embeded Where and ForEach:

(
<your code>
).Where( {
    $_.Name -like "$wordToComplete*"
 }).ForEach( {
    [System.Management.Automation.CompletionResult]::new($_.Name, $_.Name, 'ParameterValue', $_.Name)
 })

This will work faster than:

(
<your code>
) | Where-Object {
     $_.Name -like "$wordToComplete*"
} | ForEach-Object {
     [System.Management.Automation.CompletionResult]::new($_.Name, $_.Name, 'ParameterValue', $_.Name)
}

[mklement0]

@B-Art, there are two options, which aren’t mutually exclusive:

• If you feel the documentation is lacking / needs correction / a new topic should be created, open issues (and possible create PRs) at the documentation repo, https://github.com/MicrosoftDocs/PowerShell-Docs/issues (you can also create an issue direct from an existing online help topic to suggest a correction or improvement to it, specifically.

• If you (possibly in addition) want to share PowerShell tips, use a forum such as Stack Overflow (you can ask a question that describes your scenario and then self-answer).

  • That said, you may find that such tips already exist; for instance, this answer discusses the relative performance of the ForEach-Object cmdlet vs. the .ForEach() array method, and this answer shows use of the parameter-level [ArgumentCompleter()] attribute.

Other forums:

• The Slack and Discord community chat forums (they seamlessly talk to each other).

• The PowerShell.org forum for searching or posting questions about PowerShell.

<div> GitHub</div><div>MicrosoftDocs/PowerShell-Docs</div><div>The official PowerShell documentation sources. Contribute to MicrosoftDocs/PowerShell-Docs development by creating an account on GitHub.</div>

[B4Art]

Thanx again @mklement0