3 Best Useful Feature In Laravel | Backend API | Helpfull For Developer | Learn In Just 6 Minutes

Video Statistics and Information

Video
Captions Word Cloud
Reddit Comments
Captions
hello everyone welcome back to the channel so today we are going to show with you the three of the hidden features of LEL I mean we as a backend developer has worked a lot with different kind of things with LEL but there are three of the features I really like about l so I'm going to share with this with you I do not know if you have know this but if you know this it would be a great uh thing for you okay so the first thing is then the about command Okay so PHP Artis artism the about command so the about commands gives you a glimpse of everything in your LEL project right from the environment to the catch to the drivers to everything but what I have done is that I have created a custom section for this uh command to be executed so here you can keep any kind of things like informations like the uh keys or any kind of development information that you wanted to uh keep hidden from everyone but you want it here so all the developers know pH partion about and then they can unreveal that information but it it is not SE to generalize public right okay so this is something very very useful so how I have done this I will come to the uh I'm come to the that actually okay so if you go into this section and if you go into the app service provider app service provider and you can write this about command and you can write anything you can even increase the keys over there like anything like this so whatever keys I have put in two keys type and author so you can key put any kind of keys and you can create this command exactly okay so this is one of the useful features so number one number two two is the API response this is a game changer for me okay so this is a traditional API I have written I'm writing apas a lot but this is the traditional way I write apas like the status message response okay so now if you go to the list modified and if you click on this API it also gives you the same type of response but you will say what is the difference between these two the difference lies in how we create them so this is the traditional way I called apis right or create apis right the response object has been created and all those has been created and then this is repeated in all the stuff but in the modified I have not done that I have created a app service provider a micros service a response micros service that use the return structure right you can not only use for this return you can use for numerous type of things in L like you can do a calculation you can do something like differentiating things you can send out response on submission of the forms so this micros service is been very useful and you can see the values are coming in you can put an array also you just return that array itself so this microservice is controlled or you can put a statistics um over here and just uh send it there so this micros service helps me a lot so there is no structure anymore no no more response no more like writing each and every line of it and then it's just a structure okay it can be created in different way but this is a proper way to create it actually it can be created by a helper function also but this is a proper way this microservice is a proper way and microservice always used a lot of things it's inbu structure of the LEL itself so this is the second feature that I have I very useful to the third one is something different the we Clause okay so you might be thinking that where Clause are all the same no it's not that when you are doing a production Gade application these kind of things matter so here you can see what I have written I've written the product where relationship where user status and zero so I'm creating a relationship between so it's a creating a left joint exactly but I'm not writing a joint here it's where relationship exactly so I can even write the query like this user product purchase count is greater than one and oh sorry here is something user product purchase count is greater than one okay so this query will run like the same you have here on a joint point but it is much more simplier way it's much more simplier way so if you go if so if you are writing a lot of joints these days you have to write a lot of joints of different tables so this is going to be a game chain and very full handy so how I have created this is that I have just created on the products I've just created a relation between the product and the user and obviously the user ID is being saved on the user P exactly okay so this is how I have created the relationship exactly and uh this is how I'm calling this so these are the key features of laravel these are the very Diamond features of laravel that I use in a production grade application to simplify things out I hope this video helps you a lot I will be submitting the code and on the description yeah keep watching keep cing and if you like my videos do subscribe to my channel thank you so much for watching this video
Info
Channel: Code 180
Views: 67
Rating: undefined out of 5
Keywords: Laravel, API, Backend, Developement, 3 Use Full Fetaure Of Laravel
Id: kUgJLik_YPs
Channel Id: undefined
Length: 6min 6sec (366 seconds)
Published: Fri Apr 19 2024
Related Videos
Note
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.