Blade {{ multi-line

[Zizaco]

As discussed here
( https://github.com/laravel/laravel/issues/647 )
it seems a good idea to be included.

I'm here posting this issue because i'm facing a 180+ characters line between {{ }} right now. :(

[machuga]

IMO multi-line would ultimately be counter-productive in trying to encourage less logic in views, along with just slightly complicating the parsing.

[Zizaco]

I agree with you, but there are some things that seems to be views respondability that will be ubberly better with multi-line.
Imagine you using a form builder:

Form::select('month', [
    '01' => 'January',
    '02' => 'February',
    '03' => 'March',
    '04' => 'April',
    '05' => 'May',
    '06' => 'June',
    '07' => 'July',
    '08' => 'August',
    '09' => 'September',
    '10' => 'October',
    '11' => 'November',
    '12' => 'December',
]);

or

Form::open(
    URL::action(
        isset( $action ) ? $action : 'Admin\StuffController@store',
        isset( $stuff ) ? ['id'=>$stuff->id] : []
    ),
    isset( $method ) ? $method : 'POST' 
) 

or even an form that is not meant to be reused

Form::open(
    URL::action( 'Admin\StuffController@store'),
    'POST',
    ['class'=>'myformclass otherclass']
) 

Even a simpler thing may look messy in one line:

{{ HTML::action( 'Admin\StuffController@edit', $stuff->title, ['id'=>$stuff->id], ['class'=>'btn btn-primary'] ) }}

Ok, i'm using Meido/Form and Meido/Html but I'm not shure if there is some alternative that can do a big difference in the terms of "being legible in one line".

[machuga]

Examples 1-3 above I would say should not be done like that in the view, and are mostly examples of my point.

Example 1: Use a config file or something for the dates, then it's a short single line. No need to render inline

Example 2: This seems like you may be abstracting at the wrong level. That's a lot of logic for opening a form. A lot of this resolution, if needed as such, could be done in a composer or some other layer. Additionally, you could also simply use a form partial, and have Form::open()/close() inside create.blade.php and edit.blade.php, each calling the partial in the middle. You could also make a helper or form macro for this kind of thing.

Example 3/4: While ~ 110 chars is not terribly optimal, it is still essentially logic free. I don't see breaking it into multiple lines to be a way of increasing it's readability since it is to be acting as an HTML tag, which in regards to the opening tag w/ attributes would not otherwise be broken across multiple lines if it was of equal length.

[Anahkiasen]

@machuga If Blade wanted to encourage people to not write logic in their views then let's remove @if and @else and all the other ones no ?
Also the <?php ?> tags I mean, those are accessible too right ?

This must be the first I ever see someone going against code readability.

Form:: and HTML:: are removed, since it is considered bad practice.

<link href="{{ path('to/my/style.css') }}" />

[Anahkiasen]

Well there still are a lot of packages for them out there.

[JonoB]

I agree with @machuga

View can contain presentation logic, and should contain not application logic. @if and @else and @foreach etc can be used for presentation logic. Most of the above examples are application logic.

And since when are Form:: and HTML considered bad practice? This is not the reason they were removed.

[machuga]

@Anahkiasen conditionals and loops often fit in the scope of presentation logic, and other times are abstracted (render_each()), when used judiciously they can keep your templates very readable. The PHP tags are accessible, but notice they are not in scope of this conversation - PHP is PHP, you can do what you want, but doesn't mean it's appropriate. While there are still libraries that use this multi-line style, it does not meant it is "good practice". Single line statements in views are generally more readable than multi lines - opening a block in an area that is non-block based is much different from executing a statement. This is not solely scoped to Blade, but also templating - but Blade is currently supporting it whether intentionally or not with single line echos.

You accuse me of going against code readability, when I am in fact trying to propose the opposite and have stated why. Hopefully this helps you understand where I am coming from a bit better.

[spencerdeinum]

I think the blade braces, as a rule, do pretty well at showing you when you might want to refactor.

That is not to say it is perfect, not being able to do a newline in {{}} is a bit odd, but to be honest it keeps the implementation a lot easier.

The way I see it, if you need to switch to the PHP tags then you need to think about what you are doing in your View. That is not to say it is always wrong, it just might "smell" a bit.

I don't disagree with this functionality but I think keeping the implementation simple is good, especially since you can still use "normal" PHP in blade templates anyways.