-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Expose ConvertToJson as an API #8123
Copy link
Copy link
Closed
Labels
Committee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionIssue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.The issue is fixed.WG-Cmdlets-Utilitycmdlets in the Microsoft.PowerShell.Utility modulecmdlets in the Microsoft.PowerShell.Utility module
Description
Metadata
Metadata
Assignees
Labels
Committee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionIssue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.The issue is fixed.WG-Cmdlets-Utilitycmdlets in the Microsoft.PowerShell.Utility modulecmdlets in the Microsoft.PowerShell.Utility module
Type
Fields
Give feedbackNo fields configured for issues without a type.
We have ConvertFromJson exposed as an API, but not ConvertToJson.
If we had both, folks that are writing apps that host PowerShell could access Convert*Json via the API rather than needing to use a runspace!
I think we could simply convert what's in
ConvertTo-Jsonto C# and put it in thisJsonObjectclass and then haveConvertTo-Jsonjust call that API.