[5.6] Another blade helper @dd()

[laurencei]

Following on from @csrf and @method blade helpers - the other one I find myself wanting is @dd.

If you've ever had to debug a silly view issue, you might have done {{ dd($var) }} in the past to track it down.

Now you can just do @dd($var) which is much quicker and easier IMO. Can also do @dd($var1, $var2) etc.

[Modelizer]

Would not be it good if we make it like <?php call_user_func_array('dd', $args); ?>?

[GrahamCampbell]

Better to have dd(...$args) actually.

[vinterskogen]

I think because of $args is a string, that olso contains parentheses symbols.

[laurencei]

This is literally making a string containing the dd() function - not actually running the function.

$args is a string as passed by blade. So you cant do things like dd(...$args) or call_user_func_array etc - because that turns @dd($var1, $var2) into <?php dd(...($var1, $var)); ?>. This is how blade directives work. 🤷‍♂️

It works perfectly as is (I've tested it against live code). This is just a shortcut for the dd() function and therefore it already runs dd(...$args) under the hood.

[Modelizer]

Okay, 👍 Then please make changes in the doc block that $args param is an array... It will pass an array and compiler will convert it into <?php dd(...$args); ?>

[laurencei]

@Modelizer - its not an array. It's a string. That's what Blade passes and generates.

[Modelizer]

then please make it $arg it's making me crazy because $args is always use for an array 😅

[vinterskogen]

The idea is great! ;)

[GrahamCampbell]

Thanks, but 👎. I don't see the need for this, the original code you posted there looks fine.

[taylorotwell]

Going to hold off on this for now. :)

[taylorotwell]

Eh, it's fine I guess but let's not get carried away 😄

[browner12]

it feels like we're getting carried away. I personally am against the @csrf and @method, because the next thing someone is going to ask for is @form and @input and @textarea, and now we're back to the days of our Form builders.

[joshmanders]

I'd have to side with @browner12 here. What's the benefit of using @dd($var1) over {{ dd($var1) }}? the saving of having to type the mustache template tags?

Same with @csrf and @method.

[DxCat]

For me, semantically I think @dd() is better than {{ dd() }} since we're not actually inserting/echoing something into the template. The behavior and it's usage is not similar to the usual {{ $var }} or
{!! $var !}}

Although {{ dd($var) }} would work, it would actually compiles down to <?php echo e(dd($var)); ?>
while this @dd() would just compile to <?php dd(123); ?>.

For @csrf and @method though, I don't think they're needed too.

[vinterskogen]

Actually the purpose of helpers like (@dd or @dump) is completely different from examples like @form, @input or @textarea, by the reason they are focused on helping developer to debug an app (and convenient for some situations), and not focused on creating actual interface elements. Creating interface elements, I agree, is responsibility of Form-Builders like 'laravelcollective/html'. Maybe placing them to a saparate satellite-package for blade makes sense.