Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127883
Precedence: bulk
MIME-Version: 1.0
References: <CAEKnhAF3KOGcWZ6CYxpWkpZbNOGo79DD7p=WsAoJvqdJ5xG_Uw@mail.gmail.com>
In-Reply-To: <CAEKnhAF3KOGcWZ6CYxpWkpZbNOGo79DD7p=WsAoJvqdJ5xG_Uw@mail.gmail.com>
Date: Sat, 5 Jul 2025 00:49:38 +0300
Message-ID: <CAPyeZ4NuyVmzJ2W_8Ayy=mrY+9nURqMa9JKJfXyTSV9FsFGNuA@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] JSON Schema validation support
To: Jakub Zelenka <bukka@php.net>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001fc7d3063921790b"
From: udaltsov.valentin@gmail.com (Valentin Udaltsov)

--0000000000001fc7d3063921790b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sta, 5 July 2025=E2=80=AFat 00:04, Jakub Zelenka <bukka@php.net> wrote:

> Hello,
>
> I would like introduce and open discussion for RFC proposing the addition
> of JSON Schema validation support to JSON extension:
>
> https://wiki.php.net/rfc/json_schema_validation
>
> If this is successful, it should be just the first for further
> improvements (see the future scope).
>
> Kind regards,
>
> Jakub
>

Hi, Jakub!

I like the idea. I have a couple of initial thoughts:

1. Wouldn't it make sense to place all the new classes under the `Json`
namespace, similar to how it=E2=80=99s done in `ext-random`?
2. If there=E2=80=99s no way to interact with the `JsonSchema` class, what =
purpose
does it serve? Wouldn=E2=80=99t it be simpler to just extend `json_decode()=
` with
an optional `?string $schema =3D null` parameter?

--=20
Kind regards,
Valentin

--0000000000001fc7d3063921790b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>On Sta, 5 July 2025=E2=80=AFat 00:04, Jakub Zelenka &=
lt;<a href=3D"mailto:bukka@php.net">bukka@php.net</a>&gt; wrote:</div><div =
class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div dir=3D"ltr">Hello,<div><br></div><div>I would like =
introduce and open discussion for RFC proposing the addition of JSON Schema=
 validation support to JSON extension:</div><div><br></div><div><a href=3D"=
https://wiki.php.net/rfc/json_schema_validation" target=3D"_blank">https://=
wiki.php.net/rfc/json_schema_validation</a></div><div><br></div><div>If thi=
s is successful, it should be just the first for further improvements (see =
the future scope).</div><div><br></div><div>Kind regards,</div><div><br></d=
iv><div>Jakub</div></div>
</blockquote></div><div><br>Hi, Jakub!<br><br>I like the idea. I have a cou=
ple of initial thoughts:<br><br>1. Wouldn&#39;t it make sense to place all =
the new classes under the `Json` namespace, similar to how it=E2=80=99s don=
e in `ext-random`?</div><div>2. If there=E2=80=99s no way to interact with =
the `JsonSchema` class, what purpose does it serve? Wouldn=E2=80=99t it be =
simpler to just extend `json_decode()` with an optional `?string $schema =
=3D null` parameter?</div><div><br></div><span class=3D"gmail_signature_pre=
fix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"l=
tr">Kind regards,<br>Valentin</div></div></div>

--0000000000001fc7d3063921790b--