I don't see any value in the change. If we plan to move new .Net Json API and follow the API behavior the change makes no sense at all.

Ilya (@iSazonov) From what I understand you want to take away the ability to choose depth right? Why do you want to limit how people use PowerShell? Some choices may make no sense to you, but for other people, it makes a lot of sense. NET is NET, PowerShell is PowerShell - they serve a different purpose.

What does depth 0 mean?

Travis Plunk (@TravisEz13) #13660 describes why I want Depth 0.

The short of it is that depth 0 is "flat" with no nesting at all.

$Object = [PSCustomObject] @{
    AnotherObject  = @{
        Test = 0
    }
    AnotherObject1 = @{
        LetsSett = 'dfdf'
        OhNo     = @{
            OrAnotherLevel = @{
                AndAnother = @{
                    Color = [System.Drawing.Color]::AliceBlue
                }
            }
        }
    }
}
$Object | ConvertTo-Json -Depth 1

Output:

{
    "AnotherObject":  {
                          "Test":  0
                      },
    "AnotherObject1":  {
                           "OhNo":  "System.Collections.Hashtable",
                           "LetsSett":  "dfdf"
                       }
}

What I'm after:

{
"AnotherObject":"System.Collections.Hashtable",
"AnotherObject1":"System.Collections.Hashtable"
}

Of course for nested hashtables the visual part will be bad. But what I'm after actually is same behavior:

$Object | ConvertTo-Html -Fragment

Output:

<table>
<colgroup><col/><col/></colgroup>
<tr><th>AnotherObject</th><th>AnotherObject1</th></tr>
<tr><td>System.Collections.Hashtable</td><td>System.Collections.Hashtable</td></tr>
</table>

Can you rebase to try to fix the errors?

Travis Plunk (@TravisEz13) fixed

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

Travis Plunk (@TravisEz13) are we doing this ?

I wrote a bunch of tests for my own ConvertTo-jsonLiteral which has a difference by default having Depth 0 and has additional settings such as BoolAsString, NumberAsString, DateTimeFormat where you can push how the date is formatted as a string, and NewLineFormatting. I do all that because I want it sometimes to behave like ConvertTo-HTML + usually JSON based queries for REST API don't like types or other stuff from native cmdlets.

Maybe it will help, as most of the tests should work on the original cmdlets as I try to validate it with PowerShell implementation with a difference of testing additional parameters in most cases. But I do tests arrays, strings, enums and so on.

https://github.com/EvotecIT/PSSharedGoods/blob/master/Tests/ConvertTo-JsonLiteral.Tests.ps1

Feel free to copy/adjust and enhance if you see any benefit.

GitHub

EvotecIT/PSSharedGoods

PSSharedGoods is little PowerShell Module that primary purpose is to be useful for multiple tasks, unrelated to each other. I've created this module as “a glue” between my other modules. - Evo...

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

Just a gentle reminder Travis Plunk (@TravisEz13) :-)

Somebody please help to fix the CI error.

PRASOON KARUNAN V (@kvprasoon) It seems unrelated to the PR, please rebase.

PRASOON KARUNAN V (@kvprasoon) I see unrelated commits. Please fix your rebase.

Ilya (@iSazonov) ohh yeah...donno how did this happen, was doing the changes from different laptops. Will fix it.

Ilya (@iSazonov) Travis Plunk (@TravisEz13) Closing and I've created a fresh one here #14830