URI

[taylorotwell]

URI parsing and mutation powered by league/uri.

$uri = Uri::of('https://laravel.com')
    ->withQuery(['name' => 'Taylor'])
    ->withPath('/docs/installation')
    ->withFragment('hello-world');

$uri->scheme();
$uri->host();
$uri->user();
$uri->password();
$uri->path();
$uri->port();
$uri->query()->all();
$uri->query()->has('name');
$uri->query()->missing('name');
$uri->query()->decode();

// And more...

return (string) $uri;

URI instances can be retrieved from the current request, as well as created from URLs and names routes for the current application:

$uri = $request->uri();

$uri = Uri::to('/something')->withQuery(...);

$uri = Uri::route('named-route', ['user' => $user]);

URIs can even be returned directly from routes to generate a redirect to that location:

return Uri::route('named-route', ['user' => $user])->withQuery(['name' => 'Taylor']);

[stevebauman]

This looks awesome! 🎉

[shaedrich]

Awesome! Thanks to @stevebauman for your pioneer work in #53370 🎉 👏🏻

[tontonsb]

Tbh the API seems really smooth and making it Responsable feels natural now that I see it.

Love that you've chosen to go the immutable path using withers. Maybe it's worth adding the readonly keyword to class fields? Or maybe even mark both classes as readonly to communicate that the instances never change their state?

One more thing that I'd like to bring up — parse_str is older than the web standards (RFCs) and its behaviour on some edge cases is different from what people might expect to be the "correct" parsing. Have you considered using League\Uri\QueryString::parse() instead?

[korkoshko]

@taylorotwell

Query parameters can include dots in their names, which is perfectly valid. But when using data_set with parse_str, unexpected behavior can happen:

$uri = Uri::of('https://dot.test/?foo.bar=baz');

dump([
    (string) $uri->withQuery(['foo.bar' => 'zab']),
    (string) $uri->replaceQuery(['foo.bar' => 'zab']),
]);

Output:

^ array:2 [
  0 => "https://dot.test/?foo_bar=baz&foo%5Bbar%5D=zab"
  1 => "https://dot.test/?foo.bar=zab"
]

What's happening:

1. data_set: It treats foo.bar as a nested array and converts it into ['foo' => ['bar' => 'zab']].
2. parse_str: It replaces dots with underscores (e.g., foo.bar becomes foo_bar) because PHP doesn’t allow dots in variable names.

So in the first case, foo.bar turns into both foo_bar and foo[bar], which isn’t what you’d expect.

P.S The League Query component avoids using parse_str entirely to prevent these kinds of issues.

[taylorotwell]

@korkoshko I've made withQuery and replaceQuery more consistent in how they handle dot notation.

[a21ns1g4ts]

You seem to be reading my thoughts