-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Closed
Labels
Committee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionIssue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or moreWG-Cmdlets-Utilitycmdlets in the Microsoft.PowerShell.Utility modulecmdlets in the Microsoft.PowerShell.Utility module
Description
ConvertTo-Json and ConvertFrom-Json are both baked into Microsoft.PowerShell.Utility. They are highly useful given the number of web services that accept/return JSON, but they also have their fair share of limitations and/or issues. I would like to see some of those fixed, but not just for PowerShell 6.0, for downlevel versions of PowerShell as well (ideally back as far as PowerShell 3.0 unless there is a technical reason not to support that version).
Is it asking too much to move these two commands into their own JSON module so that they can be managed outside of PowerShell Core, in such a way that they can also be used for downlevel systems, even if on downlevel PS the module would have to be manually imported to get those fixes?
Metadata
Metadata
Assignees
Labels
Committee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionIssue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or moreWG-Cmdlets-Utilitycmdlets in the Microsoft.PowerShell.Utility modulecmdlets in the Microsoft.PowerShell.Utility module