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 6CFF34575E; Wed, 7 Aug 2024 17:01:11 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 52D744028C; Wed, 7 Aug 2024 17:01:11 +0200 (CEST) Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by mails.dpdk.org (Postfix) with ESMTP id EC5494027B for ; Wed, 7 Aug 2024 17:01:09 +0200 (CEST) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 224C4FEC; Wed, 7 Aug 2024 08:01:35 -0700 (PDT) Received: from [10.1.39.35] (JR4XG4HTQC.cambridge.arm.com [10.1.39.35]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 3E78A3F766; Wed, 7 Aug 2024 08:01:08 -0700 (PDT) Message-ID: <6deabc9d-1f5d-4706-8a8e-95d3df1e632c@arm.com> Date: Wed, 7 Aug 2024 16:01:06 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [RFC v1 0/1] dts: separate allowed values from json schema Content-Language: en-GB To: Nicholas Pratte , paul.szczepanek@arm.com, juraj.linkes@pantheon.tech, 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> From: Luca Vizzarro In-Reply-To: <20240807140831.27558-2-npratte@iol.unh.edu> 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 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