public inbox for bitbake-devel@lists.openembedded.org
 help / color / mirror / Atom feed
From: Rob Woolley <rob.woolley@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH v2 3/9] bitbake-setup.schema.json: Use anyOf for non-disjoint subschemas
Date: Tue, 7 Apr 2026 08:02:44 -0700	[thread overview]
Message-ID: <20260407150250.104135-4-rob.woolley@windriver.com> (raw)
In-Reply-To: <20260407150250.104135-1-rob.woolley@windriver.com>

The oneOf keyword is for matching exactly one subschema.

However, the 2 possible BitBake configuration fragments
are not disjoint. Since a simple example with type and
description would match both. For this reason, we should
use anyOf instead.

This resolves the following jsonschema linting error:
  A `oneOf` where all branches have disjoint types can be safely
  converted to `anyOf` (oneof_to_anyof_disjoint_types)

Signed-off-by: Rob Woolley <rob.woolley@windriver.com>
---
 setup-schema/bitbake-setup.schema.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/setup-schema/bitbake-setup.schema.json b/setup-schema/bitbake-setup.schema.json
index 3324546de..f2e466c9b 100644
--- a/setup-schema/bitbake-setup.schema.json
+++ b/setup-schema/bitbake-setup.schema.json
@@ -92,7 +92,7 @@
                                 "type": "array",
                                 "description": "List of BitBake configuration fragments to enable",
                                 "items": {
-                                    "oneOf": [
+                                    "anyOf": [
                                         {
                                             "type": "string",
                                             "description": "Configuration fragment name"
-- 
2.49.0



  parent reply	other threads:[~2026-04-07 15:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 15:02 [PATCH v2 0/9] bitbake-setup JSON Schema: Fix linting errors Rob Woolley
2026-04-07 15:02 ` [PATCH v2 1/9] bitbake-setup.schema.json: Add title for schema Rob Woolley
2026-04-07 15:02 ` [PATCH v2 2/9] bitbake-setup.schema.json: Add examples property Rob Woolley
2026-04-07 15:02 ` Rob Woolley [this message]
2026-04-07 15:02 ` [PATCH v2 4/9] bitbake-setup.schema.json: Remove trailing period Rob Woolley
2026-04-07 15:02 ` [PATCH v2 5/9] layers.schema.json: Add missing schema Rob Woolley
2026-04-07 15:02 ` [PATCH v2 6/9] layers.schema.json: Add title for subschema Rob Woolley
2026-04-07 15:02 ` [PATCH v2 7/9] layers.schema.json: Add examples property Rob Woolley
2026-04-07 15:02 ` [PATCH v2 8/9] layers.schema.json: Remove trailing period Rob Woolley
2026-04-07 15:02 ` [PATCH v2 9/9] layers.schema.json: Fix typo in property name Rob Woolley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260407150250.104135-4-rob.woolley@windriver.com \
    --to=rob.woolley@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox