[Question] @forelse and other missing

[Anahkiasen]

A lot of Blade was trimmed down in the making of Laravel 4, and while some I can do without, I found the @forelse loop really useful and clean, is there any plan to bring it back ?

[jasonlewis]

Not sure.

But I'd 👍 to see it brought back for sure.

[taylorotwell]

There was a slight bug in @forelse actually and I just wanted to address it. I do plan to try to bring it back in.

[Zizaco]

👍

[stsaranchin]

👍

[stormpat]

Before is comes to L4 you could just do:

@if (count($artist->albums) > 0)
@foreach ($artist->albums as $artistalbum)
{{ $artistalbum->albumTitle }}
@else
This artist has no albums
@endif

[Anahkiasen]

Well that's what I do of course but that adds a lot of clutter.

[taylorotwell]

@forelse is pretty tricky to actually implement properly. going to deprecate it.

[casoetan]

Been battling with the forelse loop for upwards of an hour till I saw this. Thanks @gkunno

@if (count($artist->albums) > 0)
  @foreach ($artist->albums as $artistalbum)
    {{ $artistalbum->albumTitle }}
  @endforeach
@else
  This artist has no albums
@endif

[ibrasho]

@taylorotwell, want kind of trickiness is involved?
We can come up with a decent solution.

SMARTY (optional else):

{foreach $myArray as $item}
    <li>{$item}</li>
{foreachelse}
    <li>Nothing to show</li>
{/foreach}

HANDLEBARS (optional else):

{{#each myArray}}
    <li>{{this}}</li>
{{else}}
    <li>Nothing to show</li>
{{/each}}

why not BLADE?

@foreach($myArray as $item)
    <li>{{$item}}</li>
@else
    <li>Nothing to show</li>
@endforeach

[robclancy]

Because it is deprecated, that's why. I'm sure you can handle it.