New Laravel Challenge: Improve API Controller Code

I didn't plan to shoot this video, but received a comment and thought "why not make it a challenge" :)

Let's go!

- - - - -
Support the channel by checking out our products:

[LaravelDaily]

Ok, I've reviewed 11 PRs and put a smiley on their description as my "stamp of approval" :)
For others, you may look into the first PRs or review each other's code.
Conclusion: there are many ways to do the same things of validation, API returns, etc. This challenge will inspire at least a few videos in the near future.

[debjit]

Thank you for this exercise. I just updated the repo. Created a file pretending it is a request file created using PHP artisan.

[mateusssantana]

Hi, Povilas. First of all i would like to thanks for your videos, they're very helpfull to the laravel community! I have a suggestion for a video: how to run queue jobs when running laravel in multiple instances? Imagine you have three containers (eg: aws infrastructure) running the same laravel project. When a job is sent to the queue, how to avoid that this job to be executed by all instances? The Laravel's system queue already manage it? And when running schedule jobs? So, just some suggestions :)

Thanks you one more time!

[nicolasromero]

hi thank you for share your videos, you know a package to make a server side rendering for SPA in vuejs?? i have a spa but now the SEO be compromise cos' the render is not in a server. thanks from Brasil

[noplay]

Hey you made some videos about multi tenancy. But I haven't really found a video about multi-instance. I know it's more devops related than laravel. But I'd be interested in your approach.

[Luthfi]

Very good exercise, one that i needed

[santanudas]

if in a form nothing is required but at least one have to select or user can select all or according to their need then how should I manage the query ? Thanks in advance sir.

[vladyslavbondarenko]

Greetings sir! Thanks for your educational videos!

I have some kind of model like User, users have a type like Admin and Client. And they must have different fields. For example, the Client has a phone number and an address, but the Admin does not need these fields. A scenario is possible that at some point the User can become an Admin. Perhaps this task is typical, but I want to do everything right so that in the future it will be possible to add more types of users or certain fields to a certain type of Users.

It will be great to hear from you! Thank you! Good luck!

[nutandahal]

please make one video sir.. how can we use db transaction on multiple big fan from nepal sir .

[helderneves]

First I would create a Trait just for responses

[LocalInfoMaker]

Please make a laravel API project ... I need to learn

[intipontt]

I don't think this warrants an entire project. Just a few files changed. It's taking too long to download the laravel boilerplate at the moment of writing.