Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filling Gaps in the PowerShell Language #719

Open
6 of 27 tasks
StartAutomating opened this issue Nov 23, 2023 · 0 comments
Open
6 of 27 tasks

Filling Gaps in the PowerShell Language #719

StartAutomating opened this issue Nov 23, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@StartAutomating
Copy link
Owner

StartAutomating commented Nov 23, 2023

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

Command

JSON

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

HTML

HTML can ConvertTo, but nothing else.

Module

ModuleMember

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

Object

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant