Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:124088 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id A4E7C1A009C for ; Sun, 30 Jun 2024 12:02:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1719749021; bh=13eawGVHJZJBTrFLO8TJcO5TkOhrDzUv30ikv+Un+tA=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=ELaR1r2YBYR/i6TEMWssLplfovQVPHSb2SsAZVR6h1HMoRIlubpac3la5cdIK4EVM zol95RZPwrDRP7e0QGilZ+h3Jzn4R274Sf1Wi9MBSqbTTsWkElaxAsB4jn9bhMQc+n ZGBXGT5keTxlaXYWMG86uh5lUxp4Cuq+zQBHBf1MpThM3G/t4hrBSRMmYga3hWgy0G dWixjB3qjnuaFmlaeq11CqPH7dYZyklpdmn17uwMv/0cCImNo8OWikblv3MpAl0cku tfGZ7erS8K0j39oH8Sqr8BmhkHkjxhQ1Kf98s25ZwXVnQDV9n5+9Ku8gInk49Tf0lC LHcELWcNmrvYA== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E4022180D81 for ; Sun, 30 Jun 2024 12:03:40 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sun, 30 Jun 2024 12:03:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1719748939; bh=JQ5S9vjONKl31waa7OUktRzcPCvYNNYmgNc0GVVQ+Fk=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type:from:to:cc:subject:message-id; b=FVwkWzGX0zxV0lHnJo4cYWsHex8pJezGpVjAgu5IH+Fzt9dlyMDgx9dHPoP3qWq37 TRlyNINxefx0a0QpmQbsb/QQN5tEJN/8oDVYAKOYP+b2YDxWNgQCmER3hY+9dwy8N4 IWiz4R7TXBQazcS/8BfRN2OVhCHZWVAQAvW1HlmcUk3I5hBoZA3AESSDcT50D3MolU 4HtSogAfEUUMhAf5RH9hu78TqfyqnyvmUveGVx5FXYnYywpD3WQbR6YyblOnSHNWmz q9yY91OA6MA7n6GuN/LmW4bW0yLoMwoaspscC/rxK3Kdlxm84N9oaUJ9PsdPRxtyzC K8dWaN74T42DA== Message-ID: <66420855-9900-48a8-9964-b9dda81a8bdc@bastelstu.be> Date: Sun, 30 Jun 2024 14:02:18 +0200 Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net MIME-Version: 1.0 Subject: Re: [PHP-DEV] [RFC][Discussion] Enhance JSON error messages To: juan carlos morales , "Gina P. Banyard" Cc: PHP Internals List References: Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=) Hi On 6/28/24 15:49, juan carlos morales wrote: > Suggested by Jakub Zelenka (the main arquitect of the JSON part in php > basically), in the PULL REQUEST is better to create a brand new > function to have detailed error messages when json encoding, decoding, > validating, fails. For the folks following along, I've commented on the PR. I think that improving the existing messages is the right choice, not adding new functions that users will need to remember to use. Best regards Tim Düsterhus