Title: Test-Json in 7.7.0 writes no error when a 'not' keyword fails, e.g. in if/then (follow-up to #28218; #28273 fix is 7.6-only) · Issue #28438 · PowerShell/PowerShell · GitHub
Open Graph Title: Test-Json in 7.7.0 writes no error when a 'not' keyword fails, e.g. in if/then (follow-up to #28218; #28273 fix is 7.6-only) · Issue #28438 · PowerShell/PowerShell
X Title: Test-Json in 7.7.0 writes no error when a 'not' keyword fails, e.g. in if/then (follow-up to #28218; #28273 fix is 7.6-only) · Issue #28438 · 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/28438
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Test-Json in 7.7.0 writes no error when a 'not' keyword fails, e.g. in if/then (follow-up to #28218; #28273 fix is 7.6-only)","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\nFollow-up to #28218. In 7.6 that issue was fixed by #28273, which put `TestJsonCommand` back on `OutputFormat.List`. 7.7.0 does not have that fix. It stays on `OutputFormat.Hierarchical` and reports errors with the recursive `ReportValidationErrors`. The repros in #28218 pass on 7.7.0. The symptom from #28218 is back for a different schema shape, though: `Test-Json` returns `False` and writes **no error** when the failing keyword is `not`. The common case is a conditional such as \"if `Subdomain` is absent, `TenantKey` must not be `admin`\":\r\n\r\n```powershell\r\n$cases = [ordered]@{\r\n 'top-level not' = '{\"not\":{\"enum\":[1]}}', '1'\r\n 'nested not' = '{\"properties\":{\"k\":{\"not\":{\"enum\":[\"admin\"]}}}}', '{\"k\":\"admin\"}'\r\n 'if-not-required/then' = '{\"if\":{\"not\":{\"required\":[\"s\"]}},\"then\":{\"properties\":{\"k\":{\"not\":{\"enum\":[\"admin\"]}}}}}', '{\"k\":\"admin\"}'\r\n 'array item if/then' = '{\"properties\":{\"c\":{\"type\":\"array\",\"items\":{\"if\":{\"not\":{\"required\":[\"s\"]}},\"then\":{\"properties\":{\"k\":{\"not\":{\"enum\":[\"admin\"]}}}}}}}}', '{\"c\":[{\"k\":\"admin\"}]}'\r\n}\r\nforeach ($n in $cases.Keys) {\r\n $sc, $j = $cases[$n]; $e = $null\r\n $r = Test-Json -Json $j -Schema $sc -ErrorVariable e -ErrorAction SilentlyContinue\r\n \"{0,-22} returned {1}, errors {2}\" -f $n, $r, @($e).Count; $e | % { \" [$_]\" }\r\n}\r\n```\r\n\r\n### Expected behavior\r\n\r\n```console\r\nEvery case returns False and writes at least one error that names the failing location.\r\nOn 7.6.6 and 7.6.10 the two if/then cases do write an error:\r\n\r\ntop-level not returned False, errors 0\r\nnested not returned False, errors 0\r\nif-not-required/then returned False, errors 1\r\n [The JSON is not valid with the schema: Required properties [\"s\"] are not present at '']\r\narray item if/then returned False, errors 1\r\n [The JSON is not valid with the schema: Required properties [\"s\"] are not present at '/c/0']\r\n```\r\n\r\n### Actual behavior\r\n\r\n```console\r\nPS 7.7.0\r\ntop-level not returned False, errors 0\r\nnested not returned False, errors 0\r\nif-not-required/then returned False, errors 0\r\narray item if/then returned False, errors 0\r\n```\r\n\r\n### Error details\r\n\r\n```console\r\nNo error is written. That is the bug.\r\n```\r\n\r\n### Environment data\r\n\r\n```powershell\r\nName Value\r\n---- -----\r\nPSVersion 7.7.0\r\nPSEdition Core\r\nGitCommitId 7.7.0\r\nOS Microsoft Windows 10.0.26300\r\nPlatform Win32NT\r\nPSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}\r\nPSRemotingProtocolVersion 2.4\r\nSerializationVersion 1.1.0.1\r\nWSManStackVersion 3.0\r\n```\r\n\r\n### Visuals\r\n\r\n**Version comparison** (same script, Windows x64):\r\n\r\n| Case | 7.6.6 | 7.6.10 | 7.7.0 |\r\n|---|---|---|---|\r\n| top-level `not` | 0 errors | 0 errors | 0 errors |\r\n| nested `not` | 0 errors | 0 errors | 0 errors |\r\n| `if`/`then` with `not` | 1 error | 1 error | **0 errors** |\r\n| array item `if`/`then` with `not` | 1 error | 1 error | **0 errors** |\r\n\r\n**Likely cause:** with `OutputFormat.List`, 7.6 reports every failing node in the flat list. That includes the `required` inside the `if`'s `not`. The error text is misleading, but it does tell the user that validation failed and where. 7.7.0 uses `OutputFormat.Hierarchical` and walks only nodes where `IsValid` is false (`ReportValidationErrors`, which came from #26618). The failing node is the `not` keyword under `then`. Its subschema is *valid*, so the walk skips it. The `not` node has no error message of its own, so nothing is written. The `not` cases already write nothing on every version. 7.7.0 adds the `if`/`then` cases to that list.\r\n\r\n**Suggested fix:** when a node fails but neither it nor any of its children produced an error message, write a generic error for that node's `InstanceLocation` and `EvaluationPath`, for example `Value should not validate against the 'not' schema at '/k'`. It would also help to extend the #28218 regression tests with a `not` case and an `if`/`then` case.\r\n\r\n**Impact:** scripts that wrap `Test-Json ... -ErrorAction Stop` in `try`/`catch`, or show `-ErrorVariable` to users, get `False` with no explanation, and no exception for the `catch` to handle. We found this when our config-validation tests failed on the 7.6.10 → 7.7.0 upgrade.\r\n","author":{"url":"https://github.com/UncleBats","@type":"Person","name":"UncleBats"},"datePublished":"2026-11-17T13:19:39Z","url":"https://github.com/PowerShell/PowerShell/issues/28438"}
| 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:35a81ef3-9de0-414a-18cc-7e79383aaab7 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 8E3C:255994:27AF53:346B94:6AFD1537 |
| html-safe-nonce | 8e6d8ada62354882d85b569edb7010adf3a00a185de6429860e169eb6d724fec |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4RTNDOjI1NTk5NDoyN0FGNTM6MzQ2Qjk0OjZBRkQxNTM3IiwidmlzaXRvcl9pZCI6IjI4MzI2OTA3NTM1MzUwMjIzOTEiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | ade54e280376e43942e120098bbbc9c3f8b3728be81a17addd3928215f0e974b |
| hovercard-subject-tag | issue:6445470476 |
| 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/28438/issue_layout |
| twitter:image | https://opengraph.githubassets.com/31023b7d1dad55624b5b373ec087f4a70c2c4f126d1f0ea862d137cd1032141a/PowerShell/PowerShell/issues/28438 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/31023b7d1dad55624b5b373ec087f4a70c2c4f126d1f0ea862d137cd1032141a/PowerShell/PowerShell/issues/28438 |
| 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 | 7c34e25df4e46e972c8f0225e63410231bdeb9ea5634597c712796bbcdb2e627 |
| 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 | 8fa571ebaa95e4e6bf872197c0e84b7dc48e6785 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width