DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Vizzarro <Luca.Vizzarro@arm.com>
To: Nicholas Pratte <npratte@iol.unh.edu>,
	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
Subject: Re: [RFC v1 0/1] dts: separate allowed values from json schema
Date: Wed, 7 Aug 2024 16:01:06 +0100	[thread overview]
Message-ID: <6deabc9d-1f5d-4706-8a8e-95d3df1e632c@arm.com> (raw)
In-Reply-To: <20240807140831.27558-2-npratte@iol.unh.edu>

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

  parent reply	other threads:[~2024-08-07 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 14:08 Nicholas Pratte
2024-08-07 14:08 ` [RFC v1 1/1] dts: split enums from primary " Nicholas Pratte
2024-08-09 15:43   ` Jeremy Spewock
2024-08-07 15:01 ` Luca Vizzarro [this message]
2024-09-10  9:34   ` [RFC v1 0/1] dts: separate allowed values from " Juraj Linkeš

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=6deabc9d-1f5d-4706-8a8e-95d3df1e632c@arm.com \
    --to=luca.vizzarro@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=dmarx@iol.unh.edu \
    --cc=jspewock@iol.unh.edu \
    --cc=juraj.linkes@pantheon.tech \
    --cc=npratte@iol.unh.edu \
    --cc=paul.szczepanek@arm.com \
    --cc=probb@iol.unh.edu \
    --cc=yoan.picchi@foss.arm.com \
    /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;
as well as URLs for NNTP newsgroup(s).