Router shouldn't handle query parameters

[piotr-cz]

At this moment, URLs with query parameteres have to be defined as routes: /homescreen=1

In my opinion, a definition like / should work, but it doesn't.

[aheinze]

hi,

sorry I don't get your intention. could you please give a more detailed example?

thanks!

[piotr-cz]

Sure.
Let's say my URL is http://www.foobar.com/?homescreen=1.

and route definition is:

$app->get('/', function($params) use ($app) { die('Home'); });

The url is not matched by the route and I have to add special new one

$app->get('/?homescreen=1', function($params) use ($app) { die('Home'); });

IMHO the route definition should match. Then I'll be able to read query parameters with $app->param('homescreen', 0).

For example FastRoute recommends stripping query string from URI (PATH_INFO in case of Lime) in basic usage example

[aheinze]

I see, but to be honest I wouldn't recommend to use the default route (using $_SERVER['PATH_INFO']) anyway.

But instead provide your own one which should be already filtered:

$app = new Lime\App([
    'route' => $route
]);

or

$app->run($route);

[piotr-cz]

Thanks, I forgot it's possible to pass route manually to lime app