Feature Request - Parameter Library
Posted: Wed May 06, 2015 11:15 am
Love this product. I've found that the module I'm working on has the same parameter in multiple commands. I would like functionality that allows me to create a library of parameters and then link a parameter in the command to the parameter in the library.
- I have 12 commands with the parameter VolumeID
- I would create a linked parameter in a parameter library called VolumeID
- I would then link the parameter for all 12 commands to that parameter in the library.
- If I update the parameter information in the library it will automatically update the parameters in all 12 commands that have that parameter linked to the library.
I am aware it is possible to copy a parameter in the Tree Navigation and paste it to a new cmdlet. However, that provides only assistance during initial implementation of the help files and doesn't provide scalable assistance when updating that parameter.
In my example I have in my parameter note a mechanism for gathering the VolumeID using another command. If that command changes then my parameter description changes. I currently need to update each iteration manually.
Implementation consideration
Seems it would be straight forward to include a net new tree navigation specifically for managing commonly used objects. This is a place I could store common parameters, examples, notes, etc. This could serve as a library. The only requirement is that I would be able to copy and paste those objects into the modules tree navigation where necessary. The next step in this would be the linking mechanism where objects in the module tree could be linked to items in the library tree.
Also to note:
Copy/paste of content is tedious when Ctrl+A doesn't work properly in the text fields of the UI.
- I have 12 commands with the parameter VolumeID
- I would create a linked parameter in a parameter library called VolumeID
- I would then link the parameter for all 12 commands to that parameter in the library.
- If I update the parameter information in the library it will automatically update the parameters in all 12 commands that have that parameter linked to the library.
I am aware it is possible to copy a parameter in the Tree Navigation and paste it to a new cmdlet. However, that provides only assistance during initial implementation of the help files and doesn't provide scalable assistance when updating that parameter.
In my example I have in my parameter note a mechanism for gathering the VolumeID using another command. If that command changes then my parameter description changes. I currently need to update each iteration manually.
Implementation consideration
Seems it would be straight forward to include a net new tree navigation specifically for managing commonly used objects. This is a place I could store common parameters, examples, notes, etc. This could serve as a library. The only requirement is that I would be able to copy and paste those objects into the modules tree navigation where necessary. The next step in this would be the linking mechanism where objects in the module tree could be linked to items in the library tree.
Also to note:
Copy/paste of content is tedious when Ctrl+A doesn't work properly in the text fields of the UI.