Description
I think the the Request::$uri could (should!?) be an instance of the Uri component, this would prevent users from having to parse it into an Uri instance again when they want to get the path or host for example.
Another option I can see is to make parts/helpers available through the Request interface, like in laravel.
A bit of backstory
The reason for this is that I tinkered with deploying a tempest app with laravel cloud, but got some client errors due to being behind a proxy and inertia (on me) passing the full request url instead o a relative one, and getting the relative url was a bit more work than it could have been ($request->uri->relative or browser inspired $request-uri->href).
Description
I think the the Request::$uri could (should!?) be an instance of the Uri component, this would prevent users from having to parse it into an Uri instance again when they want to get the path or host for example.
Another option I can see is to make parts/helpers available through the Request interface, like in laravel.
A bit of backstory
The reason for this is that I tinkered with deploying a tempest app with laravel cloud, but got some client errors due to being behind a proxy and inertia (on me) passing the full request url instead o a relative one, and getting the relative url was a bit more work than it could have been ($request->uri->relative or browser inspired $request-uri->href).