Question 1

How do you build a Laravel Todo app with CRUD using Blade?

Accepted Answer

In this episode I use the Laravel Blade starter kit and build everything with plain Blade views. I generate a Todo model, migration, and factory, then wire up resource routes and a TodoController for index/create/store/edit/update/destroy. I also paginate the list and show due dates/reminders using Carbon casts.

Question 2

How do you create resource routes for a TodoController in Laravel?

Accepted Answer

I use route::resource('todo', TodoController::class) in web.php. That gives me all the routes for listing, creating, storing, editing, updating, and deleting. I also run php artisan route:list to verify everything was generated.

Question 3

Why did you disable mass assignment in this Laravel project?

Accepted Answer

I add Model::unguard() in AppServiceProvider so mass assignment is disabled globally and I handle it myself. Then I validate everything using a Form Request and only use request->safe() data. This keeps random/malicious fields from getting through.

Question 4

How do you validate Todo fields like due date and reminder date in Laravel?

Accepted Answer

I create a TodoRequest and define rules like title required, description nullable, and due_at/reminder_at as nullable date fields. Because datetime-local sends a 'T' in the value, I use prepareForValidation to replace the 'T' with a space before validation runs. That way the dates validate cleanly.

Question 5

How do you show only the authenticated user’s todos in Laravel?

Accepted Answer

In the index method I query Todo where user_id equals auth()->id(). That ensures each user only sees their own list. I also order by reminder_at desc and paginate the results.

Question 6

How do you reuse the same Blade form for create and edit in Laravel?

Accepted Answer

I pass a Todo model to the view and check $todo->exists. If it exists, I point the form to the update route and spoof PUT; otherwise I submit to store with POST. Then I fill inputs using $todo->title, $todo->description, and so on—create stays empty because it’s a new model.

Question 7

How do you implement delete with confirmation in Blade?

Accepted Answer

I use the UI kit’s form/button components and trigger a confirmation modal before submitting. When the user confirms, the form submits with method DELETE to the destroy route. In destroy I delete the model and redirect back with a flash success message.

Episode 1 – The List That Started It All – Building The Laravel Todo App

🛍️ Products Mentioned (8)

15% DISCOUNT ON ALL PLANS OF CLOUDWAYS HOSTING FOR 3 MONTHS

DevDb extension link

Route resource documentation link

Icons link

Route model binding documentation link

Fonts, extensions I use, and Support Laratips links

Project GitHub Link

Laravel Documentation for Observer

About This Video

Frequently Asked Questions

🎬 More from Laratips