A few times I encountered a situation – a store() or update() method with Request parameter, but I needed to add some additional value to the request before calling Eloquent functions. So how to do that? Apparently, pretty easy.
Let’s look at the code:
function store(Request $request)
{
// some additional logic or checking
User::create($request->all());
}
What if you need to add additional field to the request with value coming from that additional logic block? It would look like this:
function store(Request $request)
{
// some additional logic or checking
$plan = 123; // some logic to decide user's plan
$request->request->add(['plan' => $plan]);
User::create($request->all());
}
See? The general logic is to add an array of key => value to the $request->request property.
Small tip, but hopefully helpful!
That’s a bad practise, because all Request instances will have that additional data.
Why not just do:
`User::create($request->all() + [‘plan’ => $plan]);`
or:
`User::create(array_merge($request->all(), [‘plan’ => $plan]));`
Thanks Till,
Agree with your point, though for simple store() functions there is almost no difference.
`$request->all() + [‘plan’ => $plan]` will not add the ‘plan’ key if it is already exist in a request. The `array_merge`seems more robust , although the plus-operator is much more faster.
Do you mean to say that by doing $request->request->add([‘plan’ => $plan]); Then every future request on the server for that user session will contain the additional data?
Usually i use array_merge to add more data before passed into repository model
wtf ?!
`$request->merge(array)`
How about this?
Add values to the Request array:
`array_add($request->all(), ‘user_id’, $user->id);`
Remove values from the Request array:
`array_except($request->all(), [‘screenshot’, ‘webcam’]);`
Or like this
Request::merge(array(‘user_id’ => Auth::id()));
why not
User::create($request->all(), [‘plan’ => $plan]); ?
After you *artificially* add the parameters, $request->all() doesn’t return the expected result. $request->merge() seems to be a better approach.
$request->merge() works great. Example: $request->merge([‘key1’ => ‘value1’, ‘key2’ => ‘value2’])
[…] Baca juga pos eksternal: How to “artificially” add values to Request array. […]
In laravel 5.6 we can pass parameters between Middlewares for example:
FirstMiddleware
public function handle($request, Closure $next, …$params)
{
//some code
return $next($request->merge([‘key’ => ‘value’]));
}
SecondMiddleware
public function handle($request, Closure $next, …$params)
{
//some code
dd($request->all());
}
I find this method to be useful within middleware. At the point where I have custom middleware to check if a record exists, or if a record is related to a record, I may add the record to the request.
I find this helps to be more granular with authorization (helps me when writting for apis).