Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118475 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 81926 invoked from network); 25 Aug 2022 21:03:31 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 25 Aug 2022 21:03:31 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B6BCD180505 for ; Thu, 25 Aug 2022 14:03:30 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-ua1-f52.google.com (mail-ua1-f52.google.com [209.85.222.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 25 Aug 2022 14:03:30 -0700 (PDT) Received: by mail-ua1-f52.google.com with SMTP id i5so8355835uat.6 for ; Thu, 25 Aug 2022 14:03:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc; bh=blSBwMD63pZzaq6T9xjxikB4nnvhHTdgPtQ6wQCuo4M=; b=GwZPHJcD6nAndqmFyZ44/Vn2Lv0OZ6gbOZM5IuOz9jypFUQV6+rStTIK0G6SzyxT6U w0L9qBZ6ewNdAUeel6IynO24hAsw3nx2qDjv+Y3OmhmHWWSBTgH6JXhxOWpQtTeBkVtE bOCbrqw9zSkc85U7s+a84+PXW6Jyz1T/SJRDH2eclI+gwHHC9DZ0SxcXTJW9s2W017b9 PTjHzrBCj7YwlputLUAzaZbdnCo/5G/PzNzR5pc6bsS0MeeLTED0ZoH3sGswcQVkCEzC ckcN0m3ZwIJUeR799Ov+vmPGWKQeIwb0emxjmAXeEGSA7LjObwduGiXWs3XCgommdUo9 ZzUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc; bh=blSBwMD63pZzaq6T9xjxikB4nnvhHTdgPtQ6wQCuo4M=; b=bF+T0qPDYyiFtkMrn4uQr7+mCBmuslWNAXuiwfE2SFBk0q3bInWLAujj9ysO03HiWh BFwZBnARabbBccKhkZOr584zPIreSS2BYMMNnmfqvBGdCGUjEEq7BLnqWhKCVVRuPenG BpPBseKRJrcJF3QNR3L2LUAx56HOs/yUMBEt7FL3xyrTSdovQYAAxkPI6Tnwy5KHYrse e0Al2AuscXPisq+pTvk2u0FafCQnHtX4Lnu//s5A2swFBu6pbNYb4HuTtQBhhO0tu6sv ToeJTDocCr1oa6sSYTfh2YXIEIGfhGWCPriGXKUlEr/r9KQJ4B1d4TMwMSxYwte37ZsU ns6w== X-Gm-Message-State: ACgBeo1EcYXUaVadrnbGihhYKM7L89DTlFA1ZpsDcS7k78npJ/VhNpGl hYxNUBvuxkNPMxHnsZxmjebIj9/lDNJL+eVDhXc= X-Google-Smtp-Source: AA6agR7O0G2GrhJOdQE7IXAD4ZmxQP8cPk3NN2fVxWyTCg26M6r/vhURp30XiOge3YdYS5O47GNjWrl2NcvwdOnUCXs= X-Received: by 2002:ab0:2c11:0:b0:38c:f6d4:6435 with SMTP id l17-20020ab02c11000000b0038cf6d46435mr2363908uar.66.1661461409588; Thu, 25 Aug 2022 14:03:29 -0700 (PDT) MIME-Version: 1.0 References: <30876360-1d4f-8097-0b58-fd902f1fa009@gmail.com> In-Reply-To: <30876360-1d4f-8097-0b58-fd902f1fa009@gmail.com> Date: Thu, 25 Aug 2022 23:03:18 +0200 Message-ID: To: Rowan Tommins , PHP Internals List Content-Type: multipart/alternative; boundary="00000000000020690c05e717215f" Subject: Re: [PHP-DEV] RFC json_validate() - status: Under Discussion From: dev.juan.morales@gmail.com (juan carlos morales) --00000000000020690c05e717215f Content-Type: text/plain; charset="UTF-8" Hello Rowan thanks for participating. My answer for your comments would be: === Regarding JSON_THROW_ON_ERROR === I think is a valid point from your side, and I am open to change the implementation if the maintainers believe so. I leave it there as it existed in json_decode() and wanted to give the developer the option to use it or not. But as I said, you hae a valid point, that I also like. === Regarding the examples you mentioned === The one from humhub and Symfony http-kernel, yes you are right, I will take them out from the RFC right now. Nice catch. But the Magento one, I took a look again, and I still believe is right example, because the only reason is using json_decode() for, is to validate only. Am I missing something here? Regards. RFC: https://wiki.php.net/rfc/json_validate Implementation: https://github.com/php/php-src/pull/9399 --00000000000020690c05e717215f--