You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having some problems trying to modify a request in order to dinamically accept aliases without having to explicitly define the routes. Probably I'm not doing it right, but the problem leads me to think that there is something inconsistent in the Request class.
The reason it probably has to wait for version 3 is that it is a highly used class we don't want to break BC and we need to fix some things from groud up.
I'm having some problems trying to modify a request in order to dinamically accept aliases without having to explicitly define the routes. Probably I'm not doing it right, but the problem leads me to think that there is something inconsistent in the Request class.
if I do this:
Then
$path
is/my-path
.But if I do:
Then
$path
is the original path and not/my-path
.I think it is a strange behaviour, it is error-prone and makes you take wrong assumptions.
The text was updated successfully, but these errors were encountered: