René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`ConvertTo-Json`: terminate cut off branches with a ellipsis string  rather than a full (.Net) type name","articleBody":"This enhancement request is related to:\r\n[Make ConvertTo-Json detect circular references](https://github.com/PowerShell/PowerShell/issues/6638)\r\n[In ConvertTo-Json the max allowed depth is 100. However, we should add code to dynamically check if we are running out of stack, and serialize objects with bigger depths](\r\nhttps://github.com/PowerShell/PowerShell/issues/3181)\r\n\r\nApparently almost every programmer goes through the pitfall of the default limited `-Depth` of the `ConvertTo-Json` cmdlet,\r\nSee  Sackoverflow: [Unexpected ConvertTo-Json results? Answer: it has a default -Depth of 2](https://stackoverflow.com/questions/53583677/unexpected-convertto-json-results-answer-it-has-a-default-depth-of-2)\r\n\r\nI guess this goes along with the fact that  `ConvertTo-Json` terminates branches that are deeper than the default `-Depth` (2) with a (.Net) full type name. Therefore programmers assume a bug or a cmdlet limitation and do not read the help or about. \r\nTo my opinion, adding a full type name to a terminated branch doesn’t add much value, knowing that:\r\n- Json hardly preserves any (.Net) type names at all\r\n- You can’t rebuild the object from the type name without its data.\r\n\r\nMeaning, that a simple [ellipsis]( https://en.wikipedia.org/wiki/Ellipsis) (three dots: `...`) at the end of the cut off branch could suffice and have a clearer meaning that indicates an *intentional* omission of additional child properties.\r\n\r\nDefinition of an ellipsis (from [Wikipedia]( https://en.wikipedia.org/wiki/Ellipsis)):\r\n\r\n\u003e An ellipsis (plural ellipses; from the Ancient Greek: ἔλλειψις, élleipsis, 'omission' or 'falling short') is a series of dots (typically three, such as `…`) that usually indicates an intentional omission of a word, sentence, or whole section from a text without altering its original meaning.\r\n\r\nFor compatibility, I would not use the Unicode ellipses character  (U+2026) but simply 3 (ascii) dots: …\r\n\r\nTaken the following commands:\r\n```\r\n$Test = @{Guid = New-Guid}\r\n$Test.Parent = $Test\r\n$Test | ConvertTo-Json\r\n```\r\nIn stead of producing:\r\n```\r\n{\r\n    \"Guid\":  \"a274d017-5188-4d91-b960-023c06159dcc\",\r\n    \"Parent\":  {\r\n                   \"Guid\":  \"a274d017-5188-4d91-b960-023c06159dcc\",\r\n                   \"Parent\":  {\r\n                                  \"Guid\":  \"a274d017-5188-4d91-b960-023c06159dcc\",\r\n                                  \"Parent\":  \"System.Collections.Hashtable\"\r\n                              }\r\n               }\r\n}\r\n```\r\nIt should produce:\r\n```\r\n{\r\n    \"Guid\":  \"a274d017-5188-4d91-b960-023c06159dcc\",\r\n    \"Parent\":  {\r\n                   \"Guid\":  \"a274d017-5188-4d91-b960-023c06159dcc\",\r\n                   \"Parent\":  {\r\n                                  \"Guid\":  \"a274d017-5188-4d91-b960-023c06159dcc\",\r\n                                  \"Parent\":  \"...\"\r\n                              }\r\n               }\r\n}\r\n```","author":{"url":"https://github.com/iRon7","@type":"Person","name":"iRon7"},"datePublished":"2018-12-02T18:40:45.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/8381/PowerShell/issues/8381"}