Consider removing ScriptsToProcess from manifest
bgelens opened this issue · 2 comments
bgelens commented
Polaris Bug Report
The use of ScriptsToProcess pollutes the imported modules and doesn't allow for clean removal by typing rmo polaris
Description of the bug
To remove everything imported I have to rmo polaris* as well as rmo MimeTypes.Class and rmo New-ScriptblockCallback
When ScriptsToProcess is removed, the module seems to function fine and only Polaris module is imported.
Expected behavior
Have only one module imported and allow it to be removed in one go as well.
Version Information
Run the following script and copy and paste the results here:
| Name | Version |
|---|---|
| Polaris | 0.2.0 |
| Platform | SerializationVersion | PSEdition | OS | PSCompatibleVersions | PSRemotingProtocolVersion | PSVersion | WSManStackVersion | GitCommitId |
|---|---|---|---|---|---|---|---|---|
| Win32NT | 1.1.0.1 | Core | Microsoft Windows 10.0.18290 | 1.0.-1.-1, 2.0.-1.-1, 3.0.-1.-1, 4.0.-1.-1, 5.0.-1.-1, 5.1.10032.0, 6.1.1.-1 | 2.3 | 6.1.1 | 3.0 | 6.1.1 |
jeremymcgee73 commented
I believe this is done so that the types are exported. Can you try running (Start-Polaris).GetType() with and without the ScriptsToProcess?
bgelens commented
Works ok for me
