by Devin Yang
(This article was automatically translated.)

Published - 8 years ago ( Updated - 8 years ago )

Foreword:

In the directive of Laravel 5.6.8, there is a new function called @dump
Let's see how cool he is.

Regarding the update:

Before starting, let me briefly describe my update experience this time. My last version was Laravel 5.5.33 (the version before the update).
In this update, I directly modified my composer.json to use the new version of Laravel,
Then update him directly.


After adjusting require, execute it directly for him
composer update

After updating, execute php artisan (alias) to view the version. Update 5.5.33 to 5.6.11 ..:)


The update went smoothly and executed without issue, luckily .

The above is my update experience, if you want to update like this, please be sure to test whether it is feasible in the development environment first!!

Or suggest reading the upgrade manual.
https://laravel.com/docs/5.6/upgrade


topic

Closer to home, let's take a look at the new feature @dump of the blade on 5.6 that I updated.
Here, I spit out an Array $abc from the Controller to the view for testing.

Display the results through var_dump and @dump respectively:


In the above picture, you can see that @dump super easy to use, and it can also be collapsed : (as shown below)

Cool..I like it.

 

Tags: laravel

Devin Yang

Feel free to ask me, if you don't get it.:)

No Comment

Post your comment

Login is required to leave comments

Similar Stories


docker,dlaravel

D-Laravel 1.5.5 Change Notes

D-Laravel's fpm image was rebuilt using the official dockerfile of docker php before php 7.2.1. And so I can specify that the default owner of fpm is dlaravel, --with-fpm-user=USER Set the user for php-fpm to run as. (default: nobody) --with-fpm-group=GRP Set the group for php-fpm to run as.

docker, tinkerwell, tinker, laravel

Application of Tinkerwell and docker environment

In fact, I don't use Tinkerwell recently because it keeps costing me money to update. If you want to test the direct ssh host, it’s done, isn’t it?

laravel

How do I upgrade the backend to Lravel 5.5

At the beginning, my background was a framework created by myself, which also uses MVC architecture, database connections and environment configuration files made by myself, including my own template syntax, until I want to support Restful, I have an idea, why should I rewrite the same function myself after others have written it, would it be better to write it out? So I started to use the framework, At the beginning, Slim was adopted mainly because it supports a lower version of php, but because Slim's twig templates are not as easy to use as Laravel's blade template...