Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118365
Feedback-ID: i835c46d5:Fastmail
User-Agent: Cyrus-JMAP/3.7.0-alpha0-758-ge0d20a54e1-fm-20220729.001-ge0d20a54
Mime-Version: 1.0
Message-ID: <a72a14ca-97a5-4738-8c43-2259f9dedf66@www.fastmail.com>
In-Reply-To: <C622EC5A-F2DA-4638-B93A-46A8D6407F60@automattic.com>
References: <C622EC5A-F2DA-4638-B93A-46A8D6407F60@automattic.com>
Date: Sun, 07 Aug 2022 13:02:40 +0100
To: =?UTF-8?Q?Bj=C3=B6rn_Larsson?= <internals@lists.php.net>
Content-Type: multipart/alternative;
 boundary=5db90591ae7247aca92cd831bb3f3224
Subject: Re: [PHP-DEV] Re: RFC Idea - is_json - looking for feedback
From: php@ollie.codes ("Ollie Read")

--5db90591ae7247aca92cd831bb3f3224
Content-Type: text/plain

Hey,

While I'm not opposed to the idea, I'm struggling to think of a way to accurately determine whether a string is true JSON that doesn't involve some sort of parsing.

Sure some regexes can be run on it, but I'm not sure that will ever be 100% accurate. Any parsing of the JSON to determine whether or not it's valid JSON would, in most situations, lead down a code path that then parsed the JSON again, essentially repeating the same function for little benefit.

I personally like to use the *`JSON_THROW_ON_ERROR`* flag on json_decode.

Not trying to rain on your parade, so sorry if it comes across that way, I'm just not sure of a way to do it where the benefit outweighs the cons, but then again, there are people a lot smarter than me on this list.

---
Best Regards,
*Ollie Read*

--5db90591ae7247aca92cd831bb3f3224--