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.

Commencez par reproduire le comportement dans les scripts d’exemple c:\Utils.ps1 et c:\Interface.ps1, en vous concentrant sur l’appel de fonction dot-sourced et sur la variable $itemToLog entre les fichiers. C’est terminé lorsque l’analyseur avertit au sujet de la construction demandée et fournit l’indication demandée concernant l’utilisation de la variable, avec la portée et les diagnostics attendus convenus.