Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119638
MIME-Version: 1.0
References: <CANMwmbMObQJD=bBncxXcHOgs1yoBfHXsTE1KZDYcSKMxMUUrRQ@mail.gmail.com>
 <CAEKnhAE7BSrXBv-4BQCVTSemmY1Z2XMTuj5nhv85mrSytnHvqw@mail.gmail.com>
 <CANMwmbOe2SVXg=aocB+y0m-5=9x_=PGc3YQqbD9syVW8udfS6A@mail.gmail.com>
 <CAEKnhAEpnmOPS9v27LsdiFJDigNXugs8x4HpMNJRWOhYqA+QJw@mail.gmail.com> <CABdc3WrufL2Avx3omTDAvDNjX52L4yGSnUEoLuP5cGhZY7PpAA@mail.gmail.com>
In-Reply-To: <CABdc3WrufL2Avx3omTDAvDNjX52L4yGSnUEoLuP5cGhZY7PpAA@mail.gmail.com>
Date: Wed, 1 Mar 2023 13:45:24 +0000
Message-ID: <CAEKnhAEj3SpdHuAEjJYoW0V3GGxRLmTusskkeuDQL1yJfBEFPg@mail.gmail.com>
To: =?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?= <michal.brzuchalski@gmail.com>
Cc: juan carlos morales <dev.juan.morales@gmail.com>, 
	PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003ed06705f5d6ed9f"
Subject: Re: [PHP-DEV] RFC Idea - json_validate() validate schema
From: bukka@php.net (Jakub Zelenka)

--0000000000003ed06705f5d6ed9f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

On Wed, Mar 1, 2023 at 1:36 PM Micha=C5=82 Marcin Brzuchalski <
michal.brzuchalski@gmail.com> wrote:

> Hi Jakub
>
> =C5=9Br., 1 mar 2023, 14:09 u=C5=BCytkownik Jakub Zelenka <bukka@php.net>=
 napisa=C5=82:
>
>> >
>> > Question ... are you planning to incorporate this by enhancing
>> > json_validate() ???
>> >
>>
>> Yes the plan is to initially enhance json_decode and json_validate that
>> would get a new $schema argument . I plan to create a class for the
>> actually schema as it needs to be parsed to its own representation so it
>> is
>> convenient to have it in the object. It could be also later created from
>> the different sources than just JSON string (e.g. assoc array / stdClass
>> or
>> automatic generation from the class that I mentioned before) so it will =
be
>> better to have it in the class.
>>
>> Regards
>>
>> Jakub
>>
>
> Do we really need this in core? What makes it less usable as an extension=
?
>
>
The primary motivation is that this allow stopping decoding / validation
once first invalid part is found - basically this is going to be validated
as parsed. It means this will eliminate all currently possible DOS attacks
on the actual JSON parsing. There are other reasons that we can discuss in
more details once proposed like better availability for users but those are
just secondary reasons and sort of side effects.

Regards

Jakub

--0000000000003ed06705f5d6ed9f--