Introduced by @dump, new features in Laravel 5.6.8

by Devin Yang
(This article was automatically translated.)

Published - 7 years ago ( Updated - 7 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

dlaravel

D-Laravel v1.5.0 is a new version.

1. Change the image generation method of fpm, optimize dockerfiles/fpm/php7.x/Dockerfiles, and make it easier to set and adjust extension packages. 2. Adjust docker-compose-build.yml, and in the Project directory of D-Laravel, You can quickly build your own image through ./console build. And many more changes....

laravel, livewire

livewire important notes

Before starting your Livewire journey, here are three basic considerations about public properties: 1. The property name must not conflict with a property name reserved for Livewire (such as $rules or $message) 2. Store in Data in public properties is visible to front-end JavaScript. Therefore, you should not store sensitive data in it. 3. Properties can only be JavaScript-friendly data types (string, integer, array, boolean), or one of the following PHP types: Stringable, Collection, DateTime, Model, EloquentCollection.

laravel,dotenv,seo

How do I dynamically load different dotenv files in Laravel according to the subdomain name

Before we start, let me complain. Originally, my website could automatically display different languages according to the user's browser. That's okay, but Google's SEO doesn't seem to like it. He recommends using different URLs for each language and not using cookies or browser settings to adjust the content of the page. Well, I'll just be obedient. His suggested method, the first solution: distinguish by country, such as example.tw or example.de, how is this really impossible, or buy the registered domain name, or take all the domain names and no one will take it The strange domain name is more likely. The second solution: use sub-domain names to distinguish, this is what I am going to do, and so on to explain how to do it in Laravel. The third solution: example.com/tw/ and the like, Apple seems to do it this way. The fourth solution: site.com?loc=tw and the like are not recommended, indeed I think this is not a good idea.