Replies: 3 comments
-
Does anyone have any opinion on this matter? |
Beta Was this translation helpful? Give feedback.
0 replies
-
According to the Get-PlasterTemplate cmdlet documentation, this is not how it is supposed to work. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This seems to be an issue and not a good candidate for discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've noticed that if I have several version of the same module containing a plaster template inside (even if the manifest has the same version),
Get-PlasterTemplate
cmdlet returns all instances of the templates from all the versions of the same module. So if I have the following:Running
Get-PlasterTemplate -IncludeInstalledModules
currently returns all three templates (besides the default ones). This behavior makes me want to make sure that I uninstall previous versions of such modules right after Update-Module. Is there really a need to go through all the PS Module versions instead of just the latest ones? To me it seems that going through the latest ones only should be the default behavior (similar to Import-Module) besides, it should run faster. If there's actually a need to expand all previous module versions, the functionality could still be accessible through a dedicated switch (i.e. -ExpandAllModuleVersions). There might as well also be an additional switch (i.e. -IncludeAllTemplates) to list out all template instances even if their versions are identical, as follows:Beta Was this translation helpful? Give feedback.
All reactions