Filling Gaps in the PowerShell Language

[StartAutomating]

There are fairly simple scenarios that pure PowerShell does not do. Most of these revolve around "completeness" for a given noun.

To give a couple of examples for a couple of data formats:

CLIXML

Clixml has Import/Export, but lacks ConvertTo/ConvertFrom and Out

• [x] #720
• [x] #721
• [ ] #722
• [ ] #723

Command

• [ ] #1086
• [ ] #1087

JSON

JSON has ConvertFrom/ConvertTo, but not Import/Export and Out

• [x] #724
• [x] #725
• [ ] #726
• [ ] #727

HTML

HTML can ConvertTo, but nothing else.

• [ ] #728
• [ ] #729
• [ ] #730
• [ ] #731
• [x] #732

Module

• [ ] Export-Module should export a module
• [ ] #1129
• [ ] #1128
• [ ] #1131
• [ ] Split-Module should split modules into smaller parts
• [ ] #1130

ModuleMember

We can Export-ModuleMember (but not export classes), but we cannot Import-ModuleMember (having this would help modules bootstrap themselves move flexibly)

• [x] #743

Object

• [ ] #884
• [ ] Invoke-Object should allow reflected invocation
• [ ] #885
• [ ] #883
• [ ] Set-Object should perform updates to an object

Some of these commands may be pulled from Pipeworks, though dust may need to be removed and docs will need to be updated.