Suggestion for new rule - Ensure that variables used in a function is always declared in the local scope

In order to reduce the number of hard to debug errors, we run our PowerShell scripts with Set-StrictMode -Version Latest. This lets us catch issues where we e.g. have misspelled a variable name (or forgot to assign it before using it) during runtime. But it would be immensely useful to catch these kinds of errors before we run the scripts, e.g. during an automated build.

We have deployment scripts that run for quite a long time (several hours), and silly misspelled variable names or misplaced variable assignments then costs quite a bit of development time. Catching these errors early would be immensely useful.

Example of something that should cause an error:

function Get-Foobar()
{
    if ($b + 2 -gt 5)
    {
        return $b
    }

    return 5
}

This would be OK:

function Get-Foobar($b)
{
    if ($b + 2 -gt 5)
    {
        return $b
    }

    return 5
}

As would this:

function Get-Foobar()
{
    $b = 123;
    if ($b + 2 -gt 5)
    {
        return $b
    }

    return 5
}

從 issue 中的兩個 PowerShell 範例開始，檢查儲存庫中現有的 analyzer 規則和測試，以確定新規則應放在哪裡。定義應如何處理參數、指派和變數參照；完成的標準是回報未宣告變數的範例，同時兩個有效範例都通過，並為所選擇的行為提供涵蓋率。