Level 88
You get the variable as a second parameter in your function
$app->get('hello/{name}', function (Psr\Http\Message\ServerRequestInterface $request, $name) {
var_dump($name);
});
Nov 8, 2015
9
Level 1
PSR7 - how does it work with Lumen?
How do I use PSR7 with Lumen and access the HTTP request data?
My code:
$app->bind('Psr\Http\Message\ServerRequestInterface', function ($app) {
return (new Symfony\Bridge\PsrHttpMessage\Factory\DiactorosFactory)->createRequest($app->make('request'));
});
$app->get('hello/{name}', function (Psr\Http\Message\ServerRequestInterface $request) {
$name = $request->getAttribute('name');
var_dump($name);
});
And then in my URL:
http://example.com/public/hello/world
So with $name = $request->getAttribute('name'); I should get world but I get NULL instead.
Any ideas?
Level 56
As mentioned above it is not a request parameter but a route parameter so you get it as a parameter of your callback function.
Level 1
It totally works differently from Slim 3 and Zend Expressive!
I don't need a second parameter (which does not look neat) but only $name = $request->getAttribute('name');
So which one does it correctly then??
Level 56
It is a route parameter so you get it as an argument of your action callback. If for some reason you want to retrieve it like this pass it as an url query parameter.
Level 1
ok. probably i should stick with Expressive or Slim then.
Level 88
It's just the way Laravel works... And of course it works different from other frameworks!
Route parameters: http://laravel.com/docs/5.1/routing#route-parameters
Level 56
What is the problem about this ?
Level 1
I thought it should it works to comply with PSR 7.
Level 56
I thought it should it works to comply with PSR 7.
I dont think psr7 specify how route parameter should be handled. Does it ?
Please or to participate in this conversation.