Title: Test-Json in 7.6.7 writes no error for violations nested below the first level (e.g. array items) · Issue #28218 · PowerShell/PowerShell · GitHub
Open Graph Title: Test-Json in 7.6.7 writes no error for violations nested below the first level (e.g. array items) · Issue #28218 · PowerShell/PowerShell
X Title: Test-Json in 7.6.7 writes no error for violations nested below the first level (e.g. array items) · Issue #28218 · PowerShell/PowerShell
Description: Prerequisites Write a descriptive title. Make sure you are able to repro it on the latest released version Search the existing issues. Refer to the FAQ. Refer to Differences between Windows PowerShell 5.1 and PowerShell. Steps to reprodu...
Open Graph Description: Prerequisites Write a descriptive title. Make sure you are able to repro it on the latest released version Search the existing issues. Refer to the FAQ. Refer to Differences between Windows PowerSh...
X Description: Prerequisites Write a descriptive title. Make sure you are able to repro it on the latest released version Search the existing issues. Refer to the FAQ. Refer to Differences between Windows PowerSh...
Opengraph URL: https://github.com/PowerShell/PowerShell/issues/28218
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Test-Json in 7.6.7 writes no error for violations nested below the first level (e.g. array items)","articleBody":"### Prerequisites\n\n- [x] Write a descriptive title.\n- [x] Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)\n- [x] Search the existing issues.\n- [x] Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).\n- [x] Refer to [Differences between Windows PowerShell 5.1 and PowerShell](https://learn.microsoft.com/powershell/scripting/whats-new/differences-from-windows-powershell).\n\n### Steps to reproduce\n\nThis is a regression from 7.6.6 to 7.6.7. When a schema violation is nested deeper than one level (for example an array item), `Test-Json` still returns `False`, but it no longer writes an error that says what is wrong or where. Violations at the top level are still reported.\n\n```powershell\n$schema = '{\"type\":\"object\",\"properties\":{\"top\":{\"type\":\"string\"},\"list\":{\"type\":\"array\",\"items\":{\"type\":\"string\",\"pattern\":\"^[a-z]+$\"}}}}'\n\n'{\"top\":1}' | Test-Json -Schema $schema -ErrorVariable e1 -ErrorAction SilentlyContinue\n\"errors: $($e1.Count)\"; $e1 | % { \" $_\" }\n\n'{\"list\":[\"ok\",\"NOT OK\"]}' | Test-Json -Schema $schema -ErrorVariable e2 -ErrorAction SilentlyContinue\n\"errors: $($e2.Count)\"; $e2 | % { \" $_\" }\n```\n\n### Expected behavior\n\n```console\nPS 7.6.6\nFalse\nerrors: 1\n The JSON is not valid with the schema: Value is \"integer\" but should be \"string\" at '/top'\nFalse\nerrors: 1\n The JSON is not valid with the schema: The string value is not a match for the indicated regular expression at '/list/1'\n```\n\n### Actual behavior\n\n```console\nPS 7.6.7\nFalse\nerrors: 1\n The JSON is not valid with the schema: Value is \"integer\" but should be \"string\" at '/top'\nFalse\nerrors: 0\n```\n\n### Error details\n\n```console\nNo error is written. That is the bug.\n```\n\n### Environment data\n\n```powershell\nName Value\n---- -----\nPSVersion 7.6.7\nPSEdition Core\nGitCommitId 7.6.7\nOS Microsoft Windows 10.0.26200\nPlatform Win32NT\nPSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}\nPSRemotingProtocolVersion 2.4\nSerializationVersion 1.1.0.1\nWSManStackVersion 3.0\n```\n\n### Visuals\n\n**Likely cause:** the 7.6.7 servicing change behind #28205 / #28214 (\"Disable fetch delegate on $ref feature…\") switched `TestJsonCommand` from `OutputFormat.List` to `OutputFormat.Hierarchical` without also backporting the recursive error reporting from `master`.\n\n- **v7.6.6** evaluates with `OutputFormat.List`. That output is flat, so iterating `evaluationResults.Details` once reaches every error.\n- **v7.6.7** evaluates with `OutputFormat.Hierarchical` (`_evaluationOptions`, line ~143), but `ProcessRecord` still calls `HandleValidationErrors` on the root and its *direct* `Details` only (lines ~287–295). Any error deeper than that, such as `/list/1`, is never written.\n- **master** also uses `Hierarchical`, but reports errors with a recursive `ReportValidationErrors` that descends into `nestedResult.Details`, so it does not have this problem.\n\nBackporting the recursive `ReportValidationErrors` to `release/v7.6` should fix it. It would also help to add a test that asserts an error is written for a nested or array-item violation.\n\n**Impact:** scripts that use `-ErrorVariable` to show users *why* validation failed now get `False` with no details. We found this when our config-validation tests failed on the 7.6.7 upgrade.","author":{"url":"https://github.com/UncleBats","@type":"Person","name":"UncleBats"},"datePublished":"2026-10-15T12:11:46Z","url":"https://github.com/PowerShell/PowerShell/issues/28218"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:327dc288-7a68-ed4f-f802-98d3aefe4eae |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | A0AE:36D300:422522:572396:6AFCE9E1 |
| html-safe-nonce | b822c5705582f6cd2a8a5b81966832b8eb0d31092ddc813132773caeeabc59c8 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBMEFFOjM2RDMwMDo0MjI1MjI6NTcyMzk2OjZBRkNFOUUxIiwidmlzaXRvcl9pZCI6IjE5NzcxNjY2MTQyOTc4OTc0NDEiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | b88f913ce3f86e7003eb15fa8b60d50a07a4d7907469a6b52a6adf09977c5d01 |
| hovercard-subject-tag | issue:5865856618 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/PowerShell/PowerShell/28218/issue_layout |
| twitter:image | https://opengraph.githubassets.com/34cadfb9f6c2cadaa2ad40d8e186c8ee26ad891f4ccb017b2da5e8cec3eeed3b/PowerShell/PowerShell/issues/28218 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/34cadfb9f6c2cadaa2ad40d8e186c8ee26ad891f4ccb017b2da5e8cec3eeed3b/PowerShell/PowerShell/issues/28218 |
| og:image:alt | Prerequisites Write a descriptive title. Make sure you are able to repro it on the latest released version Search the existing issues. Refer to the FAQ. Refer to Differences between Windows PowerSh... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | UncleBats |
| hostname | github.com |
| expected-hostname | github.com |
| None | 99aede4c5f55ec5cf06666a8c9e03ebf9f85f7231223e7f1c38c16e5504835b3 |
| turbo-cache-control | no-preview |
| go-import | github.com/PowerShell/PowerShell git https://github.com/PowerShell/PowerShell.git |
| octolytics-dimension-user_id | 11524380 |
| octolytics-dimension-user_login | PowerShell |
| octolytics-dimension-repository_id | 49609581 |
| octolytics-dimension-repository_nwo | PowerShell/PowerShell |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 49609581 |
| octolytics-dimension-repository_network_root_nwo | PowerShell/PowerShell |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | ecfd63ca125ec74b42f74eeb158b3fa081c8c497 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width