From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 306EE45954; Tue, 10 Sep 2024 11:34:10 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 19949427B6; Tue, 10 Sep 2024 11:34:10 +0200 (CEST) Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com [209.85.167.50]) by mails.dpdk.org (Postfix) with ESMTP id EE8C7402A1 for ; Tue, 10 Sep 2024 11:34:08 +0200 (CEST) Received: by mail-lf1-f50.google.com with SMTP id 2adb3069b0e04-53659867cbdso6553977e87.3 for ; Tue, 10 Sep 2024 02:34:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pantheon.tech; s=google; t=1725960848; x=1726565648; darn=dpdk.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=UkGERowDfIEh6AejDqFzKjS0CKy7rxnM18maUcDzKzE=; b=IJkPKF8HF98Wto0ij0uwDMPSV/gIsgnpL/YNLKMt6aA3OnyIRNPNDuT1/SAWwJ+OgI 5skE3pRjcPhjjN9rKdlLkRnfIRPMizURpSs97fLIxxYDNLPs3k+Q4UFEqEXh7RhjDCcc 5ZMA893n1PjuYztIlgOMhYDiEcbBOU5A/zVE8zPqwTfgP50doOv3mk921tQcaT+CJmTL YOJXr+BjNLI92kGWvnXNKe2ynMj/6Wgm/G8ySqtiVIZp41M420yQvbu9KAgv3RI11byU TgIhya7Drsh+BRTR8mNekPJKt1cqnsoWKkV+GELm1nsmkZtgdVCE5IyeOivpOkT4eDaO SNww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725960848; x=1726565648; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=UkGERowDfIEh6AejDqFzKjS0CKy7rxnM18maUcDzKzE=; b=X4sXhM0JKgmlUwiNdvC7cs5yOaaxMJqIt+JZK5jiPUOAlWRZ9TugKABFh6EZThEIXI qGuhB8hGW53A4IfsVa3//vzMLKCgHQpILTQk6/p2xNYSYTFLN3SdPUAu/UIVmd/2yUoG l1/JRnBtJAFuTBSexDocqlH8T5Pw6P3KREARY0qm6asIh2ilLUrKiJNepJiFL3GHPlaF mgKiJPbNVNwYbHKwpK9QUoDMHpRNEEMWP1y63ESc/wcQY06eyvFx5bINwsu3XuC/1VAS HB5IQYMqDj8A81jgh/CWFqdIYGuDdh7q/Xo5+uHZn+UjPCj3KzzyyXrX95yDCwAmSJiy yNIQ== X-Gm-Message-State: AOJu0Yw3BVcOXVZKGxhpLi9IpCg5sxIRHn407bI7qzFYJ+OY2SJFE0qW wNkB1XYMlDkiv1nlBfvpYlv794NAJEdbtcsNMggQq/m4N/5C91vLAwiZJh9Ncq8= X-Google-Smtp-Source: AGHT+IFO7MlbiMH0FS96x2kzPhbjaclhQfuxF8CyiXWB6SQr9cNjplOTxui49VGAm1JQSsnH7yI++g== X-Received: by 2002:a05:6512:3a85:b0:535:6951:9e1c with SMTP id 2adb3069b0e04-536587ada96mr11802883e87.15.1725960848031; Tue, 10 Sep 2024 02:34:08 -0700 (PDT) Received: from [10.12.0.236] (81.89.53.154.host.vnet.sk. [81.89.53.154]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a8d25952761sm455606366b.59.2024.09.10.02.34.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 10 Sep 2024 02:34:07 -0700 (PDT) Message-ID: <39b1945e-593f-4d4f-b3ea-8bcd4b13ce8a@pantheon.tech> Date: Tue, 10 Sep 2024 11:34:06 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [RFC v1 0/1] dts: separate allowed values from json schema To: Luca Vizzarro , Nicholas Pratte , paul.szczepanek@arm.com, jspewock@iol.unh.edu, dmarx@iol.unh.edu, yoan.picchi@foss.arm.com, Honnappa.Nagarahalli@arm.com, probb@iol.unh.edu Cc: dev@dpdk.org References: <20240807140831.27558-2-npratte@iol.unh.edu> <6deabc9d-1f5d-4706-8a8e-95d3df1e632c@arm.com> Content-Language: en-US From: =?UTF-8?Q?Juraj_Linke=C5=A1?= In-Reply-To: <6deabc9d-1f5d-4706-8a8e-95d3df1e632c@arm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On 7. 8. 2024 17:01, Luca Vizzarro wrote: > Hi Nicholas, > > Thank you for the proposal. The way I see it is that JSON schema can be > very developer unfriendly to read, therefore I would not rely on it for > this purpose. Adding $refs as well could start making it more > complicated for this purpose. It's helpful for structuring and > maintaining the files though. > > Normally, a schema is meant for validation purposes. And docs should > provide the developer with the right information. > > Nonetheless, I am getting started in replacing Warlock with Pydantic. > And basing the Python classes on Pydantic models. Unfortunately, this > will nullify this work altogether, as Pydantic provides an automatic > facility for generating the JSON schema, thus removing the need for > manual maintenance. > > Best, > Luca What Luca says makes a lot of sense. Let's not bother improving the schema since it'll be obsolete soon with the Pydantic changes.