René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Check whether a module references itself in 'NestedModules' field in the .psd1 file","articleBody":"This feature ask is per discussion in https://github.com/PowerShell/PowerShell/pull/6843#discussion_r187123774.\r\n\r\nImporting a ill-structured module could result in a circular nested module. For example, for the following code, you will see 'True' as the output.\r\n```\r\n$testdir = Join-Path $env:TEMP test\r\n$testpsm1 = Join-Path $testdir test.psm1\r\n$testpsd1 = Join-Path $testdir test.psd1\r\nmkdir $testdir \u003e $null\r\nSet-Content $testpsm1 -Value \"function bar {}\"\r\nSet-Content $testpsd1 -Value \"@{ ModuleVersion = '0.0.1'; RootModule = 'test'; NestedModules = @('test') }\"\r\n\r\n$m = Import-Module $testpsd1 -Pass\r\n$m -eq $m.NestedModules[0]\r\n\u003e True\r\n```\r\n\r\nSo maybe a rule can be written to check the bold part of `test.psd1` \"@{ ModuleVersion = '0.0.1'; RootModule = 'test'; **NestedModules = @('test')** }\", to make sure the author is warned when a module like `test.psd1` has itself as a nested module.","author":{"url":"https://github.com/daxian-dbw","@type":"Person","name":"daxian-dbw"},"datePublished":"2018-05-10T23:05:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/997/PSScriptAnalyzer/issues/997"}