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 tried to use normal strings instead of parameters ($1) in controller calling.
$routes->get('/sth-abc', 'App::sth/foo', ['subdomain'=>'']);
$routes->get('/sth/abc', 'App::sth/foo', ['subdomain'=>'']);
In the case route is defined as: '/sth-abc', everything works as expected - www.host.com/sth-abc shows page returned by App::sth with foo as first parameter. In the second case when route is '/sth/abc' www.host.com/sth/abc returns 404.
I'm not sure if it is bug, because there is no example like this in docs but it can be a useful feature.
The text was updated successfully, but these errors were encountered:
I thought we had fixed it, but there might be a bug still in the routing that doesn't like have a leading slash in the "from" portion of the route. Try rewriting that more like this:
I tried to use normal strings instead of parameters ($1) in controller calling.
$routes->get('/sth-abc', 'App::sth/foo', ['subdomain'=>'']);
$routes->get('/sth/abc', 'App::sth/foo', ['subdomain'=>'']);
In the case route is defined as: '/sth-abc', everything works as expected - www.host.com/sth-abc shows page returned by App::sth with foo as first parameter. In the second case when route is '/sth/abc' www.host.com/sth/abc returns 404.
I'm not sure if it is bug, because there is no example like this in docs but it can be a useful feature.
The text was updated successfully, but these errors were encountered: