PSUseToExportFieldsInManifest creates unnecessary warnings

[twwilliams]

This rule complains about empty or wildcard values in FunctionsToExport, CmdletsToExport, VariablesToExport, and AliasesToExport even if there are no members of that type to export in the module. I find myself having to exclude this rule on every module manifest I run it against since I don't have any module where all four values could be filled out in the same manifest.

[kapilmb]

@twwilliams The motivation behind this rule is to allow faster module auto-discovery and thereby provide better experience (please see issue #434).

You can easily prevent the rule from from triggering for any field that does not export anything by setting the field's value to an empty list. For example, suppose your module doesn't export any variables, then you can do, VariablesToExport = @().

[twwilliams]

Well, shoot. I'm sorry. I thought I tried that last night and still got the error. Clearly, though, I didn't because I just went back and removed the ExcludeRule setting in my Pester test and it worked as expected. My apologies for the spurious report. And thank you very much for the quick response. You may close this issue at this point.

[kapilmb]

@twwilliams No worries at all.