Re: [RFC] [Discussion] Add WHATWG compliant URL parsing API
| From: | Stephen Reay | Date: | Sat, 29 Jun 2024 09:57:17 +0000 |
| Subject: | Re: [RFC] [Discussion] Add WHATWG compliant URL parsing API | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-124023@lists.php.net to get a copy of this message | ||
> On 29 Jun 2024, at 04:48, Niels Dossche <dossche.niels@gmail.com> wrote:
>
> - It's a bit of a shame that the PSR interface treats queries as strings.
> In Javascript we have the URLSearchParams class that we can use as a key-value storage for
> query parameters.
> This Javascript class also handles escaping them nicely.
Agreed this is a weird choice to me, but I'm also not surprised by weird choices via
php-fig (log level constants I'm looking at you)
We hear all the time how userland is more flexible and can change quicker - and yet here we see a
potential built in class having a worse api because it wants to be compatible with an existing
userland interface with the same bad api....
Cheers
Stephen