Re: [RFC] [Discussion] Followup Improvements for ext/uri
| From: | Rob Landers | Date: | Mon, 01 Dec 2025 21:19:37 +0000 |
| Subject: | Re: [RFC] [Discussion] Followup Improvements for ext/uri | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-129489@lists.php.net to get a copy of this message | ||
On Mon, Dec 1, 2025, at 21:50, Máté Kocsis wrote:
> Hi Everyone,
>
> I'd like to introduce my latest RFC that I've been working on for a while now:
> https://wiki.php.net/rfc/uri_followup.
>
> It proposes 5 followup improvements for ext/uri in the following areas:
> - URI Building
> - Query Parameter Manipulation
> - Accessing Path Segments as an Array
> - Host Type Detection
> - URI Type Detection
> - Percent-Encoding and Decoding Support
>
> I did my best to write an RFC that was at least as extensive as
> https://wiki.php.net/rfc/url_parsing_api had become by the end.
> Despite my efforts,
> there are still a couple things which need a final decision, or which need to be
> polished/improved. Some examples:
>
> - How to support array/object values for constructing query strings?
> (https://wiki.php.net/rfc/uri_followup#type_support)
> - How to make the UriQueryParams and UrlQueryParams classes more interoperable with the query
> string component (mainly with respect to percent-encoding)?
> (https://wiki.php.net/rfc/uri_followup#percent-encoding_and_decoding)
> - Exactly how the advanced percent-decoding capabilities should work? Does it make sense to
> support all the possible modes (UriPercentEncodingMode) for percent-decoding as well
> (https://wiki.php.net/rfc/uri_followup#percent-encoding_and_decoding_support)
> - etc.
>
> Regards,
> Máté
Hello!
For the builder methods, why not use the same wither method names? That would make switching to them
really easy, over the current implementation.
— Rob