-
-
Save ericlbarnes/5771365 to your computer and use it in GitHub Desktop.
@foreach (array_slice($posts->toArray(), 0, 5) as $post) | |
<h1>{{ $post['title'] }}</h1> | |
@endforeach |
I see usecase for that. When you use the same data two times on the same view. In one place you use all of them, but somewhere else in the same view, you need just 3. Then it's good :)
@bgallagh3r yes in an ideal situation you would just have the number you need. But some times you have special circumstances. :)
This particular use case was building a theme for an app and the $posts returned to the view was more than I needed. But other themes needed the additional. If that makes sense.
Even easier...
@foreach ($posts->slice(0, 5) as $post)
<h1>{{ $post['title'] }}</h1>
@endforeach
@briankiewel - where is that doc'd? Like to read more on it
@jrmadsen67 Unfortunately not documented on laravel.com, but you can look at the code here. It's basically just a helper for what @ericbarnes is doing, but without having to run ->toArray()
Brilliant! :)
Nice trick, thanks =)
Perfect
In my case I have One album Music with 2 discs. Each Disc 14 musics and musics came from same table music. I share with this just with the model and one single consult.. Thanks a lot its very helpful for me.
This is great. Thank you.
Perfect :) Thanks
Can you do this for an array that gets loaded from the translation files?
For example:
@foreach(trans('pages/team.team') as $teamMember)
// Do something
@endforeach
But what if I need just the first 4 or 5?
->take(20)->get();
Just needed this for a dashboard view where we need the same data in different places, just modified a bit by limiting what is shown. Thanks for the solution, worked perfectly!
@foreach ($posts->slice(0, 5) as $post)
<h1>{{ $post->title }}</h1>
@endforeach
It works perfect for me.
@foreach ($posts->take(5) as $post)
<h1>{{ $post->title }}</h1>
@endforeach
is much cleaner, and works great
Yes sir ;) @ron4stoppable
@foreach($skills->user->take(5) as $user)
this one is great
@foreach (array_slice($data, 0, 4) as $content)
thanks
Shouldn't you technically limit the posts via the controller and not via the view? I guess this might be useful when depending on a user set variable to allow them to see a certain number of posts. Just seems that if you're going to request a chunk of data you should do the request before it's sent to the view. Just wondering where you may need to do this in a use case.