René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`ConvertTo-Json` neglects to serialize ETS properties when passed output from CDXML cmdlets (CIM instances) that isn't `[psobject]` wrapped  by argument","articleBody":"### Prerequisites\r\n\r\n- [X] Write a descriptive title.\r\n- [X] Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)\r\n- [X] Search the existing issues.\r\n- [X] Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).\r\n- [X] Refer to [Differences between Windows PowerShell 5.1 and PowerShell](https://learn.microsoft.com/powershell/scripting/whats-new/differences-from-windows-powershell).\r\n\r\n### Steps to reproduce\r\n\r\nNote:\r\n\r\n* This is yet another manifestation of https://github.com/PowerShell/PowerShell/issues/5579\r\n\r\n* Note that the problem only arises for CDXML cmdlets that do not themselves wrap their output objects in `[psobject]`, such as `Get-PhysicalDisk`, `Get-VirtualDisk`, and `Get-Volume`; others, such as `Get-Disk`, _do_ perform this wrapping.\r\n\r\n```powershell\r\n# Note: Since objects passing through the pipeline are automatically [psobject]-wrapped, the following\r\n#   pipeline alternative works correctly:         \r\n#    Get-PhysicalDisk | ConvertTo-Json 3\u003e$null | ConvertFrom-Json | Format-List\r\nConvertTo-Json (Get-PhysicalDisk) 3\u003e$null | ConvertFrom-Json | Format-List\r\n```\r\n\r\n### Expected behavior\r\n\r\n```none\r\nCimClass                         : @{CimSuperClassName=MSFT_StorageFaultDomain; CimSuperClass=; CimClassProperties=System.Object[]; CimClassQualifiers=System.Object[];\r\n                                   CimClassMethods=System.Object[]; CimSystemProperties=}\r\nCimInstanceProperties            : {@{Name=ObjectId; Value={1}\\\\MKW11\\root/Microsoft/Windows/Storage/Providers_v2\\SPACES_PhysicalDisk.ObjectId=\"{47519af7-9162-11ee-9dc0-806e6f6e6963\r\n                                   }:PD:{f2881886-c54b-46f7-c1ac-8eb641e316de}\"; CimType=14; Flags=35688452; IsValueModified=False}, @{Name=PassThroughClass; Value=; CimType=14;\r\n                                   Flags=572522500; IsValueModified=False}, @{Name=PassThroughIds; Value=; CimType=14; Flags=572522500; IsValueModified=False},\r\n                                   @{Name=PassThroughNamespace; Value=; CimType=14; Flags=572522500; IsValueModified=False}…}\r\nCimSystemProperties              : @{Namespace=root/microsoft/windows/storage; ServerName=MKW11; ClassName=MSFT_PhysicalDisk; Path=}\r\nClassName                        : MSFT_PhysicalDisk\r\nUsage                            : Auto-Select\r\nOperationalStatus                : OK\r\n# ... remaining properties omitted for brevity.\r\n```\r\n\r\n\r\n### Actual behavior\r\n\r\n```none\r\nCimClass              : @{CimSuperClassName=MSFT_StorageFaultDomain; CimSuperClass=; CimClassProperties=System.Object[]; CimClassQualifiers=System.Object[];\r\n                        CimClassMethods=System.Object[]; CimSystemProperties=}\r\nCimInstanceProperties : {@{Name=ObjectId; Value={1}\\\\MKW11\\root/Microsoft/Windows/Storage/Providers_v2\\SPACES_PhysicalDisk.ObjectId=\"{47519af7-9162-11ee-9dc0-806e6f6e6963}:PD:{f2881\r\n                        886-c54b-46f7-c1ac-8eb641e316de}\"; CimType=14; Flags=35688452; IsValueModified=False}, @{Name=PassThroughClass; Value=; CimType=14; Flags=572522500;\r\n                        IsValueModified=False}, @{Name=PassThroughIds; Value=; CimType=14; Flags=572522500; IsValueModified=False}, @{Name=PassThroughNamespace; Value=; CimType=14;\r\n                        Flags=572522500; IsValueModified=False}…}\r\nCimSystemProperties   : @{Namespace=root/microsoft/windows/storage; ServerName=MKW11; ClassName=MSFT_PhysicalDisk; Path=}\r\n```\r\n\r\nThat is, only the type-native properties were serialized, not also the ETS (adapted) ones.\r\n\r\n### Error details\r\n\r\n_No response_\r\n\r\n### Environment data\r\n\r\n```powershell\r\nPowerShell 7.5.0-preview.5 on Windows (also affects Windows PowerShell)\r\n```\r\n\r\n\r\n### Visuals\r\n\r\n_No response_","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2024-11-06T22:27:23.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/24554/PowerShell/issues/24554"}