Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127899
Precedence: bulk
MIME-Version: 1.0
References: <CAEKnhAF3KOGcWZ6CYxpWkpZbNOGo79DD7p=WsAoJvqdJ5xG_Uw@mail.gmail.com>
 <9B2997E3-21C9-47D9-BB54-99C83A481ED8@php.net> <0BE9291A-A044-4660-AF80-AABE7C4B820A@php.net>
 <CAEKnhAFLRVpbwZk9Q=gdzX-vHpSta3bOonxo2QfQLK6CxwmzNg@mail.gmail.com>
In-Reply-To: <CAEKnhAFLRVpbwZk9Q=gdzX-vHpSta3bOonxo2QfQLK6CxwmzNg@mail.gmail.com>
Date: Sat, 5 Jul 2025 01:47:32 +0200
Message-ID: <CAEKnhAGj=My_Ua3dpng00p+dqMgPv64rzvsVba-LWXCmDRJkgQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] JSON Schema validation support
To: Ben Ramsey <ramsey@php.net>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c8e7a70639231e0c"
From: bukka@php.net (Jakub Zelenka)

--000000000000c8e7a70639231e0c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Jul 5, 2025 at 1:41=E2=80=AFAM Jakub Zelenka <bukka@php.net> wrote:

> On Sat, Jul 5, 2025 at 1:29=E2=80=AFAM Ben Ramsey <ramsey@php.net> wrote:
>
>> Another thing that needs to be addressed in the RFC is how error
>> reporting will work. I see this hinted at under Future Scope, but one of
>> the benefits of the existing JSON Schema Composer packages is the robust
>> level of error reporting they provide.
>>
>>
> The error reporting is done using normal error codes and exceptions get
> some sort of identification message.
>

I should probably show some example how this looks like. See this test
https://github.com/bukka/php-jsond/blob/1f640becf3cd0f0cca9c72fa5045c7ccefc=
26d7f/tests/jsond_decode_schema_002.phpt


Kind regards,

Jakub

--000000000000c8e7a70639231e0c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sat, Jul 5, 2025 at 1:41=E2=80=AFAM Ja=
kub Zelenka &lt;<a href=3D"mailto:bukka@php.net">bukka@php.net</a>&gt; wrot=
e:</div><div class=3D"gmail_quote gmail_quote_container"><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Sat, =
Jul 5, 2025 at 1:29=E2=80=AFAM Ben Ramsey &lt;<a href=3D"mailto:ramsey@php.=
net" target=3D"_blank">ramsey@php.net</a>&gt; wrote:</div><div class=3D"gma=
il_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Another thing that needs to be addressed in the RFC is how error reporting =
will work. I see this hinted at under Future Scope, but one of the benefits=
 of the existing JSON Schema Composer packages is the robust level of error=
 reporting they provide.<br>
<br></blockquote><div><br></div><div>The error reporting is done using norm=
al error codes and exceptions get some sort of identification message.=C2=
=A0<br></div></div></div></blockquote><div><br></div><div>I should probably=
 show some example how this looks like. See this test <a href=3D"https://gi=
thub.com/bukka/php-jsond/blob/1f640becf3cd0f0cca9c72fa5045c7ccefc26d7f/test=
s/jsond_decode_schema_002.phpt">https://github.com/bukka/php-jsond/blob/1f6=
40becf3cd0f0cca9c72fa5045c7ccefc26d7f/tests/jsond_decode_schema_002.phpt</a=
>=C2=A0</div><div><br></div><div>Kind regards,</div><div><br></div><div>Jak=
ub</div></div></div>

--000000000000c8e7a70639231e0c--