Clean Up Your Routes In Laravel | Learn Laravel The Right Way

Рет қаралды 2,330

Program With Gio

Күн бұрын

Пікірлер: 19

@mikulcek Ай бұрын

I really appreciate you digging deeper into underlying router implementation. It's always fun to follow along.

@ProgramWithGio 27 күн бұрын

Glad you enjoy it

@Zubbee 17 күн бұрын

This isn't useless stuff to me at all Gio. Keeping up with all you were going through was tricky but I am certainly amazed at how much thought went into the code. I want to learn to write robust code like this. I'm happy to use Laravel to build stuff no doubt, but I am intrigued and would like to learn more. Thanks for this Gio. I will watch this again for sure

@ProgramWithGio 16 күн бұрын

Glad you like it

@lairotuT-Tutorial Ай бұрын

I view this course parallel to the right way to learn PHP course. It's a really great source of knowledge and deep dive into each fragment. Thank you Gio for all this stuff! You are great! I also deeply appreciate the "stylistic" features and the explanation of your personal appraoch. Indeed on one point I follow a different approach: @3:57 you mention that you avoid inheritance for code reuse. I agree with some aspects but not with all. For me inheritance is one of the core functionalities and reasons for object oriented programming. So I agree that is makes no sense to put code into a parent class just because it is used in several child classes. But I like the idea to put code in there that is really a functionality or even parameter of every child class. Like in real life it makes it easier to understand that the separate controller only is including (and by this defining itself) with the unique stuff that it makes. Indeed I always ask myself if a new property or method is unique to this child class or if it is something that every (in this example Controller) has. If it is not every but a part of these I ask myself if the property or method is related to a subclass of the parent (then I create a sublclass in between) or if it is something that is not linkable to the objects / objecttree (then I use interface when it's varying or Trait if it's equal in every occurance).

@ProgramWithGio 27 күн бұрын

Its personal preference. I've regretted many times using inheritance, because it always starts out as simple 2-3 methods in base class that makes sense for child classes & then it grows to some giant monster that is hard to maintain. So as long as you keep it balanced & avoid stuffing a lot of things into base class that don't really belong there, you should be fine

@lairotuT-Tutorial 23 күн бұрын

@@ProgramWithGio great thanks for this evaluation! You're great!

@Odin_gospodin Ай бұрын

oooh, finally a new video, cool

@ProgramWithGio 27 күн бұрын

💙

@piotrpopawski6870 Ай бұрын

Learn it the right way, you can just group the routes give it once a controller and set prefix on the url to avoid adding on each line the "/transactions"

@ProgramWithGio Ай бұрын

Right, next episode is about route groups & how to group them properly. We cover that there. This episode is just about controllers & how to connect routes with controllers instead of using closures