Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119636 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 95515 invoked from network); 1 Mar 2023 13:09:31 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 1 Mar 2023 13:09:31 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 62FC51804F8 for ; Wed, 1 Mar 2023 05:09:30 -0800 (PST) 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.5 required=5.0 tests=BAYES_20, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, 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-ed1-f45.google.com (mail-ed1-f45.google.com [209.85.208.45]) (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 ; Wed, 1 Mar 2023 05:09:29 -0800 (PST) Received: by mail-ed1-f45.google.com with SMTP id cq23so53624456edb.1 for ; Wed, 01 Mar 2023 05:09:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Cyuu4T4/OY3XVtwc4Re/1i6TbGyWmUszS6EI7vaa5a8=; b=LrB7WIVj4YYr10Y/Y/COQJeCIvd8hhP6VYX4kvzO3mjAPneFQRX3d+iFIImztYCMG1 jyYyggpC9+ilYLKCgvzuy2F6cSVWcnxhNS0vxuMP+84s5MpSqqvwV4lHHiCl8fXRzqNU fzsIt/C/9qpY5LDj5MjjE7nBO9XW6a8wfV/MK6zY9qUVnbMMaHSbcDGlQPj1y26H04HK 2X/ArBhXxSIxXcFyLHez8TDHMDCboxzXVnRcWVfOAOeRNJs0/9dji76zJsKJeSRePzgE HVOZJVl7r0RsiOZGIAlfikqmQ1l11aKepbO/Lu7VIJdmhYPUv+MAoS4EhPQUpOo4xgOG QcRg== X-Gm-Message-State: AO0yUKUWscruS6zVa+YDRU1TLSXoECLOcWtY047KQ9B2SgXIU2VX5eM/ BKuRE52OGVDckA/wgT6CwUXEzmkDCG7Uz1NtP4s= X-Google-Smtp-Source: AK7set/eOHAO6EN7n4YNgBHoCvc4NghsJoDdDcEC4mSx1rF2raxZjfv8FF5aG1M+NCMJzKnJXo33pyKzWRqr208Lq04= X-Received: by 2002:a17:906:5594:b0:877:7480:c568 with SMTP id y20-20020a170906559400b008777480c568mr3244738ejp.8.1677676168761; Wed, 01 Mar 2023 05:09:28 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 1 Mar 2023 13:09:07 +0000 Message-ID: To: juan carlos morales Cc: PHP Internals List Content-Type: multipart/alternative; boundary="00000000000016536d05f5d66c9b" Subject: Re: [PHP-DEV] RFC Idea - json_validate() validate schema From: bukka@php.net (Jakub Zelenka) --00000000000016536d05f5d66c9b Content-Type: text/plain; charset="UTF-8" > > 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 --00000000000016536d05f5d66c9b--