Laravel Conventions/Guidelines from IxDF

[@rahulxcr]

This is very helpful

[@faridmoreno2864]

Thank you very much!!!

[@373323]

yep, that migration part is a tricky one. specially when moving from branch to branch, your database in one branch can be significantly ( and contradiction ) different than in the other branch , i think this may be a subject better tackled by an artisan command that ( dumps and stashes ) the old branch database and ( creates the new branch database ) ... food for thought

[@TalesGrechi]

I was thinking the same!

[@imqqmi]

Should work if the migration id/version is stored in database. Migration could rollback/forward as required. When automated for dev env could be made seamless.

[@codewithfongoh]

Thank you for sharing 😊

[@francescoleto2823]

Good point!

[@imnash_on_E]

Sir Laravel Daily, should I do this? public function __invoke(User $user, Request $request) Or this? public function __invoke(Request $request, User $user)

[@LaravelDaily]

I think both could work

[@krekas]

Do the second

[@imnash_on_E]

Thank you

[@MrDhump]

2nd one seems good to me.

[@ThalisUmobi]

That rollback thing seems to me super optimistic, i really don't think the effort worth it. The single action controller seems to me like an anti-pattern. The api route versioning is money though, use it, and you will thank yourself very soon.

[@khangle6872]

Single action controller is becoming the industry standard in all languages

[@ThalisUmobi]

@@khangle6872 Together with fat controllers/lean models? I mean, it seems to me that if the controller is slim, single action controllers don't bring much to the table.