Simplifying Data Removal with Laravel’s Controller Destroy Method We’re down to our last method: destroy. The destroy method will, you guessed it, remove a resource from the database. This is the simplest of the bunch. We simply need to create a link, delete a resource and return the user to the index page. https://medium.com/geekculture/laravel-p45-controller-edit-update-cmp-b16b5b77aaaa Route The route is already created. We did this a few articles ago. Route::prefix(‘/personalcars’)->group(function() { Route::delete(‘/{id}’, [PersonalCarController::class, ‘destroy’]); }); We simply need to send a delete request to our personalcars/{id} route. Creating a delete request Before we can destroy a resource, we need to be able to get there. How do you send a delete request to
Tag: Laravel Controllers
How to Use Laravel’s Controller Edit/Update Methods Effectively We have just a couple of more articles to go before we wrap up this project in its entirety. We’ll move on to more advanced topics after that. In this article, we’ll tackle how to edit a record. We’ll need to display a form with all of our form fields already populated for a particular record and then when we click update, we actually have to update our record. https://medium.com/geekculture/laravel-p44-form-single-image-upload-cmp-53c519dcd97d Our Routes The routes are already created. The edit and update routes will call the edit and update methods respectively. The edit method pulls the record from the
Controller Essentials: Understanding Laravel’s Create/Store Methods How do you insert a new record into the database? You can use tinker like we’ve been doing so far, but realistically we need to use a form. The user should see a blank form first and then click on the Submit button. The data should be sent over to another method in the controller that will help validate the data and send it to our PersonalCar model for insertion into the database. https://medium.com/geekculture/laravel-p41-controller-show-method-cmp-d503973018e7 Create The first thing that you need to see is a form. We have a route for it: it’s the route to the create method. Route::prefix(‘/personalcars’)->group(function() { Route::get(‘/create’,
Understanding the Show Method for Data Display The last article ended with us showing all of the resources in the personal_cars table. We need to be able to click on the resource and pull up the details for it. This is what the show method will do. It accepts a resource $id and then pulls the information from it. https://dinocajic.medium.com/laravel-p40-controller-index-method-cmp-f0c2b29861fc Adding the Link to Our Index View Before we can start working on the show method, we need to have a way to get to it. The route exists, so that’s one thing already cross off the list. Route::prefix(‘/personalcars’)->group(function() { // … Route::get(‘/{id}’, [PersonalCarController::class, ‘show’]); }); The user
Streamlining Laravel: Routes and Controllers High-Level Overview Now that our Model relationships are defined, we can start setting up the initial infrastructure for our routes and controllers. We’ll list out what kind of data will be sent, what we’re expecting, and then we’ll worry about creating views in the next article. https://medium.com/geekculture/laravel-p38-many-to-many-relationship-cmp-bd8847de9114 Brainstorming I’ve purposefully not created any of this beforehand. I’m writing this code as it seems natural to me. What I want to do is brainstorm on what we need to create next. We know that we have the following models: PersonalCarBrand PersonalCarModel PersonalCar Image The question is,
Simplifying Laravel: The Power of Single Action Controllers Controllers are there to make our lives simpler, not to make them more complex. However, even when we separate the logic out of our route files, sometimes the controllers themselves can also become cluttered. That’s one use case for a Single Action Controller. Laravel — P25: Passing URL Arguments to Controllers The Single Action Controller will contain a specifically named method: __invoke(). Naming the method __invoke() will eliminate the need to call it from our route. Instead, we can just call the Controller itself. Creating the Single Action Controller Creating the Single Action Controller is
Dynamic Data Handling: URL Arguments in Laravel Controllers Now that we’re familiar with creating controllers, we need to be able to pass arguments to it. This comes in form of URL parameters. Sometimes we need to pass an argument like a specific id. Laravel — P24: Controllers Intro If you haven’t created the TestController, it’s time to do so now. I’m going to be using the one from the previous article, but the artisan command to create it is: php artisan make:controller TestController. Creating the Route Our first task is to create the route. The URL will contain a parameter that will be passed
Navigating Laravel: An Introduction to Controllers For the past 23 articles, I’ve been screaming on the inside, since we haven’t been doing things the right way. Can all logic fall into your route? Sure it can. Should it? Absolutely not. This was my way easing you into Laravel. If you’ve ever read anything else on it, what’s usually the first example? “Alright guys, let’s create a to-do list.” That’s great, but it uses way too many concepts at the same time without going into enough detail about what everything else does. Enough of that, it’s time for controllers. Laravel —