Skip to content

Diagnostic ScriptName and ScriptPath properties are identical with a Powershell script rule #618

Closed
@LaurentDardenne

Description

@LaurentDardenne

When I run a custom rule :

$Result=Invoke-ScriptAnalyzer -path $pwd\test -CustomRulePath $pwd\OptimizationRules.psd1 -ExcludeRule $n -verbose

VERBOSE: Checking module 'G:\PS\PSScriptAnalyzerRules\Modules\OptimizationRules\OptimizationRules.psd1' ...
VERBOSE: Analyzing file: G:\PS\PSScriptAnalyzerRules\Modules\OptimizationRules\test\BinaryExpressionAst.ps1
VERBOSE: Running OptimizationRules\Measure-OptimizeForStatement rule.
...
VERBOSE: Analyzing file: G:\PS\PSScriptAnalyzerRules\Modules\OptimizationRules\test\MemberExpressionAst.ps1
VERBOSE: Analyzing file: G:\PS\PSScriptAnalyzerRules\Modules\OptimizationRules\test\ParenExpressionAst.ps1
VERBOSE: Analyzing file: G:\PS\PSScriptAnalyzerRules\Modules\OptimizationRules\test\ParenExpressionAst2.ps1
VERBOSE: Analyzing file: G:\PS\PSScriptAnalyzerRules\Modules\OptimizationRules\test\ParenExpressionAst3.ps1

The ScriptName and ScriptPath properties are identical :

$Result|select scriptname,scriptpath|fl *
ScriptName : BinaryExpressionAst.ps1
ScriptPath : BinaryExpressionAst.ps1

ScriptName : MemberExpressionAst.ps1
ScriptPath : MemberExpressionAst.ps1

ScriptName : ParenExpressionAst.ps1
ScriptPath : ParenExpressionAst.ps1

ScriptName : ParenExpressionAst2.ps1
ScriptPath : ParenExpressionAst2.ps1

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions