Re: RFC json_validate() - status: Under Discussion
| From: | Michał Marcin Brzuchalski | Date: | Fri, 26 Aug 2022 09:35:33 +0000 |
| Subject: | Re: RFC json_validate() - status: Under Discussion | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-118495@lists.php.net to get a copy of this message | ||
Hi Juan,
pt., 26 sie 2022 o 11:26 juan carlos morales <dev.juan.morales@gmail.com>
napisał(a):
> El vie, 26 ago 2022 a las 11:00, Michał Marcin Brzuchalski
> (<michal.brzuchalski@gmail.com>) escribió:
> >
> > A
json_decode() is a substitute that IMO solves 99% of use
> > cases.
> > If I'd follow your logic and accept every small addition that handles 1%
> of use cases, somebody will raise another RFC
> > for simplexml_validate_string or yaml_validate and the next
> PhpToken::validate.
> > All above can be valid if we trust that people normally validate 300MB
> payloads to do nothing if they DON'T fail and there is nothing strange
> about that.
> >
> > Cheers,
> >
>
> How can you make such an assertion in those numbers (99% of use cases
> and son on, that you mention) ? Can you give us more information about
> this assertions?
>
> I have provide real examples where the need to validate-only a
> json-string is actually needed, also the need from our developers
> community asking for this.
>
Your examples are a couple of functions.
Assuming that they're heavily used is as true as my assumptions.
Cheers,