Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118488 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 40839 invoked from network); 26 Aug 2022 08:56:31 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 26 Aug 2022 08:56:31 -0000 To: internals@lists.php.net Date: Fri, 26 Aug 2022 01:56:31 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.0 References: Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 172.113.137.202 Subject: Re: [PHP-DEV] RFC json_validate() - status: Under Discussion From: paul.crovella@gmail.com (Paul Crovella) Message-ID: On 8/26/2022 1:28 AM, Peter Bowyer wrote: > Hi Juan, > > On Thu, 25 Aug 2022 at 17:02, juan carlos morales < > dev.juan.morales@gmail.com> wrote: > >> RFC: https://wiki.php.net/rfc/json_validate > > > Thanks for bringing forward this RFC. I am in favour of this change, as you > can't efficiently validate JSON in userland. > > Like Rowan I'm not convinced JSON_THROW_ON_ERROR belongs here. I can't > think of a case where more than a boolean response is needed. > > Peter > I'm for this as well. Though something more than a boolean is useful to indicate when the max depth has been exceeded as that's not strictly a problem with the json's validity.