Rule Proposal: Warn on dot-sourced function

I've inherited a project where everything is in, for lack of a better description, undeclared global scope, spread across several files. Functions don't have always have parameters, and are called with a dot before the function name. Variables are treated as global, though not declared. For example:

c:\Utils.ps1

function Write-MyLog {
$itemToLog | out-file c:\mylog.txt -append
}

c:\Interface.ps1

. c:\Utils.ps1

$itemToLog = "Something happened"
. Write-MyLog

Miraculously, this all works. Of course, I dare not change anything.

I would love it if ". Write-MyLog" came up as a warning, and even more so if there were some indication that "$itemToLog" in C:\Interface.ps1 was being used by the function called from c:\Utils.ps1.

Inizia riproducendo il comportamento negli script di esempio c:\Utils.ps1 e c:\Interface.ps1, concentrandoti sulla chiamata alla funzione dot-sourced e sulla variabile $itemToLog tra file. Il lavoro è completato quando l’analizzatore avvisa in merito al costrutto richiesto e fornisce l’indicazione richiesta sull’utilizzo della variabile, con l’ambito e le diagnosi previste concordati.