[Copilot]

PR Summary

Follow-up to #2270, targeting its branch rather than main.

The review finding is reproducible: a resource-shaped call to a script-defined function is treated as a DSC declaration because command discovery uses a separate runspace. Commands inside its script block arguments are then incorrectly suppressed. Both new regression cases returned zero diagnostics before the fix instead of the two expected diagnostics.

• Recognize function declarations in enclosing script-block scopes, case-insensitively, without searching unrelated nested scopes.
• Use that information consistently for resource declarations and their same-line/following-line bodies. Do not apply implicit Get- prefix corrections to script-defined function calls; preserve explicit alias handling.
• Cover script-level and configuration-level functions, both brace layouts, unrelated scopes, and formatter behavior. Document the distinction.

Validation: .NET 8 and .NET Framework 4.6.2 builds succeeded. Alias tests: 23 passed, 2 Windows-only tests skipped on Linux. Formatter integration tests: 10 passed. Executed using PowerShell 7.4.13 and Pester 5.7.1; the configured Pester 6.0.1 package was unavailable from the accessible mirror.

PR Checklist

• PR has a meaningful title
• Summarized changes
• Change is not breaking
• All changed source files have the correct copyright header
• Added regression tests and updated documentation
• This PR is ready to merge and is not Work in Progress (opened as a draft)

[Copilot]

🟡 Changes recommended

Scoped function declarations are mishandled, causing incorrect alias rewrites and suppressed diagnostics, while repeated scope scans introduce quadratic analysis overhead.

2 open issues

• Handle scoped function declarations and visibility in analysis · New
• Index function declarations to avoid repeated AST traversal · New

What changed in this PR

This follow-up to #2270 distinguishes script-defined function calls from DSC resource declarations so alias analysis preserves function names while checking commands in their script-block arguments.

Changes:

• Adds case-insensitive function lookup in enclosing script-block scopes and reuses it in DSC classification.
• Adds regression coverage for function scope, brace layouts, unrelated scopes, and formatter behavior.
• Documents the distinction between functions, DSC resources, and implicit aliases.

File	Description
Tests/​Rules/​AvoidUsingAlias.tests.ps1	Adds function-detection and formatter regression tests.
Rules/​AvoidAlias.cs	Uses script-defined function detection in alias and DSC handling.
docs/​Rules/​AvoidUsingCmdletAliases.md	Explains function and DSC resource exclusions from implicit alias correction.

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Scope handling still changes command resolution for dot-sourced private functions and incorrectly treats script/global declarations in unexecuted nested functions as visible, causing missed diagnostics and unsafe corrections.

2 open issues

• Handle dot-sourced blocks using caller scope · New
• Keep nested script/global declarations in lexical scope · New

2 resolved since last review

• Index function declarations to avoid repeated AST traversal
• Handle scoped function declarations and visibility in analysis

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Dot-sourced scope handling still misindexes declarations and incorrectly skips script-block argument scopes, causing both erroneous alias corrections and missed diagnostics.

2 open issues

• Avoid skipping scopes for script-block command arguments · New
• Index dot-sourced declarations in the effective caller scope · New

2 resolved since last review

• Keep nested script/global declarations in lexical scope
• Handle dot-sourced blocks using caller scope

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

The argument-count restriction incorrectly treats parameterized dot-sourced blocks as child scopes, causing erroneous alias formatting and missed declarations in the caller’s scope.

1 open issue

• Fix scope handling for parameterized dot-sourced blocks · New

2 resolved since last review

• Index dot-sourced declarations in the effective caller scope
• Avoid skipping scopes for script-block command arguments

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Human assessment is needed because subtle callback scope, runspace boundaries, and function redefinition interactions can change command resolution or suppress valid diagnostics.

No open issues 🎉

1 resolved since last review

• Fix scope handling for parameterized dot-sourced blocks

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Callback scope misclassification and indexing of unreachable function declarations can change which command runs, suppress expected diagnostics, and incorrectly rewrite unreachable code.

2 open issues

• Handle caller-scoped ForEach and Where callbacks · New
• Ignore unreachable function declarations · New

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Callback-scope analysis mishandles module-qualified commands, parallel-runspace boundaries, and script blocks passed as data, causing incorrect rewrites and missed diagnostics.

3 open issues

• Stop function lookup at parallel runspace boundary · New
• Handle module-qualified callback cmdlets · New
• Exclude non-executing script-block parameter values · New

2 resolved since last review

• Ignore unreachable function declarations
• Handle caller-scoped ForEach and Where callbacks

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Callback-scope detection mishandles parameter abbreviations, switch/positional binding, and colon-attached blocks, causing valid function calls to be rewritten and diagnostics to be suppressed across parallel-runspace boundaries.

3 open issues

• Handle colon-attached callback arguments in scope detection · New
• Detect the parameter consuming callback blocks after switches · New
• Resolve parameter abbreviations before callback scope classification · New

3 resolved since last review

• Exclude non-executing script-block parameter values
• Handle module-qualified callback cmdlets
• Stop function lookup at parallel runspace boundary

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Human assessment is needed because callback-scope and command-shadowing edge cases can cause incorrect alias replacements and missed diagnostics.

No open issues 🎉

3 resolved since last review

• Resolve parameter abbreviations before callback scope classification
• Detect the parameter consuming callback blocks after switches
• Handle colon-attached callback arguments in scope detection

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Unresolved command-shadowing and callback-scope errors can cause incorrect alias replacements and suppress expected diagnostics.

4 open issues

• Stop scope lookup at all isolated execution boundaries · New
• Honor visible script-defined commands before callback scope rules · New
• Resolve callback blocks inside array arguments · New
• Resolve trailing callbacks from RemainingScripts · New

_{Review effort: Balanced}