Laravel Code Review: Validation Rules, Events, Seeds and Shorter Code 

Thanks Povilas for all the positive feedback. The Seeders were added to the migrations as I was uncertain on how to prevent them from being run multiple times while is on the dev server. I have since realised that I could just use php artisan db:seed --class=AllergenSeeder for current dev and leave it in the DatabaseSeeder class for new installations

Quick performance tip: At 8:20 in line 47. It'd be best to take out the count() function from the for loop and put it in a variable. because every loop you are executing count() function again. It might not make sense In this situation because I assume ingredients aren't that many, but in other scenarios, it might help.

At 9:11 you can add second condition inside Gate logic and use only one condition

Unless its on an older version of Laravel before it was a thing, there is a built in rule for the current password called "current_password".

well in my opinion, i would use seeder in migrations only if i need data in table right from the start, for example i have "countries" table which doesn't change a lot and i have foreign keys from "addresses" table... other example is "product_states" table i have only new and used records (maybe client will add some more later)... but nicely done factories are a bit better solution for this example... other example is maybe if a client wants a slug and not id in urls, and i don't have "slug" column... so i would make a migration, create a "slug" column in it and right after foreach record fill the column, because i will definitively forget to run seeder on deployment

wonderful review

I believe that Laravel has a default validation rule for checking and validating a given password against the authenticated user's password. I don't see why would he create a custom rule for that.

Running seeders through migrations is the most correct approach. First of all, in the CD / CI migrations will be started and you will not need to create additional conditions to run when new seeders are created in the application. How you run new seeders on a working application? Manually? Second, you can rollback at any time and delete this data if anything goes wrong. By default, seeder mechanism does not provide such an option and creating ex. RemoveUsersSeeder is simply pointless.

Thanks sir you are great :) and a gem for laravel devs

How to use two arrays in a single foreach loop ?possible?

That was awesome! 👍 So many thanks

Love this videos💙

Povilas, greetings! Could you give me an advice, please. When building an API on Laravel, what should i use for editing data on output. Eloquent Mutators or API Resources?

Can you make video about seo

Thanks, interesting!

I could actually try to send in something for code review, since I haven't gotten a CR from my more knowledgeable peers for like 2-3 solid years lol

New bad fast refactoring. At 8:03 you lost 'adults' and 'kids' values if checkbox not checked. Because there is request->has

I'm sorry, that my question is not actual for this video, but tell please, how currect in Laravel 8 remove "public" segment from url ? Thank you.

ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-qyJ_yZuV5gY.html i have question about $recipe->ingriends()->attach()... does it checks in database if hat record exists? if no, what happens if i add custom ID to dropdown or checkbox.