Those items are instantiations of our consumer classification. go back View::make('users. index')->with('users', $users); Then, we change the production of our View item a piece. We chained a brand new strategy named with(). The with() strategy permits us to go facts from the controller into the view. this system accepts arguments. the 1st argument is the identify of the variable that would be created within the view. the second one argument could be the price of that variable. To recap, now we have queried the database for all clients and handed them as an array of consumer gadgets to the view. The array of person gadgets could be to be had within the view because the variable $users considering that clients used to be the 1st argument to the with() process. Step nine – including our dynamic content material to the view Now that our view has entry to the consumer info, let's replace the view in order that we will really see these clients.

Users

@if($users)

@foreach($users as $user)
• {{ $user->real_name }} - {{ $user->email }}

@endforeach

@else seems like we have not extra any clients, but! @endif Blade is straightforward to appreciate and ends up in even more stylish code. The {{ }} tags output the result of the expression inside of them and exchange a customary echo command. different structures resembling if(), foreach(), and for() are an identical, yet with out Hypertext Preprocessor tags and with a previous @. observe Blade does not incur an important functionality penalty because it renders to a uncooked Hypertext Preprocessor cache. Parsing of a Blade template is just performed whilst adjustments were made. it is also very important to notice that you're nonetheless loose to exploit Hypertext Preprocessor tags within the Blade templates. As you will find we use an if assertion to examine if the $users array includes info. If it does, we loop during the clients and show a brand new record merchandise for every. If the $users array does not comprise any info, we output a message asserting so. and that is it! shop the dossier and hit reload on your browser, and you may see the try out account that we created. be aware this can be a great time to mess around with the HTML or upload new clients utilizing the try course that we made to get a greater think for a way every little thing works. Step 10 – RESTful controllers we now have already pointed out that Laravel's routing procedure allows you to course GET, put up, positioned, and DELETE requests to closures. yet we have not mentioned the best way to separately path them to controller activities. the answer's RESTful controllers! RESTful controllers show you how to path to various controller activities according to the request strategy. Let's configure our program to exploit RESTful controllers. on account that all of our controller sessions are derived from the Base_Controller category, we will be able to easily upload the $restful configuration to it and all of our controllers could be affected. replace your Base_Controller type to appear like this: classBase_Controller extends Controller{ public $restful = real; /** * Catch-all approach for requests that cannot be matched. * * @param string $method * @param array $parameters * @return reaction */ public functionality __call($method, $parameters) { go back Response::error('404'); } } Now, each controller that extends Base_Controller (including our personal Users_Controller) is a RESTful controller!