From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 777ED1FF146 for ; Tue, 09 Jun 2026 23:58:20 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BBD1A1BFF1; Tue, 9 Jun 2026 23:58:17 +0200 (CEST) From: Thomas Lamprecht To: pmg-devel@lists.proxmox.com, pve-devel@lists.proxmox.com, Erik Fastermann Subject: applied: [PATCH pve-common] json schema: display nested oneOf error messages Date: Tue, 9 Jun 2026 23:58:00 +0200 Message-ID: <178104227926.3211582.10078538105378154228.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260605154212.269658-1-e.fastermann@proxmox.com> References: <20260605154212.269658-1-e.fastermann@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1781042247139 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.005 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: ELBJ7GQEXWL5RYPDKOVHLVBWNJYWWSBA X-Message-ID-Hash: ELBJ7GQEXWL5RYPDKOVHLVBWNJYWWSBA X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Fri, 05 Jun 2026 17:42:12 +0200, Erik Fastermann wrote: > Correctly display the error message for each oneOf case, not just the > empty string, which was caused by the wrong key being used in the hash > lookup. Applied, thanks! [1/1] json schema: display nested oneOf error messages commit: ce033fd5bb46b280846ce28a1d57792355ee23be