3 ms·
powershell's json handling leaves a lot to be desired. It's been awhile since I poked around but I never found a good parser and usually just switch to python f
by jabroni_salad 3y ago
powershell's json handling leaves a lot to be desired. It's been awhile since I poked around but I never found a good parser and usually just switch to python for that and basically everything else to do with APIs (invoke-webrequest is really annoying to use also).
powershell is good for controlling the windows operating system and doing basic things with objects. sysadmins are more likely to have a decent time with it than developers. Although, you can use it to interpret dotnet which is kinda neat.
- tempaway41114 3y ago$myJson = Get-Content .\test.json -Raw | ConvertFrom-Json $myJson.Accounts.Users.asmith.department = "Senior Leadership" $myJson | ConvertTo-Json -Depth 4 | Out-File .\test.json from: https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/parsing-json-with-powershell/ba-p/2768721 https://techcommunity.microsoft.com/t5/core-infrastructure-a...
- hobs 3y agoAnd the depth maxes out at 100, for some reason. This is my problem with most PS data things, they work well on the surface but when you really get your hands dirty they run like dogs or have weird limitations.