Final video - How to make a Laravel CRUD API #7
HTML-код
- Опубликовано: 14 апр 2019
- Get the code from the repo here:
github.com/QuentinWatt/how-to...
Follow me on social media:
Twitter: @QuentinWatt
Facebook: @quentinwatt
Instagram: @quentinwatt
Subscribe:
/ quentinwatt
I also make videos here:
/ quentin
Donate with Paypal:
www.paypal.com/cgi-bin/webscr...
Thanks you so much dude, this was just amazing, really straght to the point, well explained, showed how things would be done manually and with laravel's utils, this series just blew my mind. I'm subscribing to check out moe laravel content
Thanks
Thank Quentin! That was straightforward and awesome!
Thank you. I'm glad you liked it.
Nice Tutorial, Easy to follow and understand!
Glad to hear that!
One of the best video I ever see!
ty m8
Thank you :)
thnak you bro help me to understanding API
Thank you for watching and commenting.
Not realizing it was over😁 Thanks!
Maybe you can make a tutorial about JWT authentication.
Well there is also Laravel Passport which is another alternative.
Thanks you so much sir..
Most welcome
please how can i display facebook and Twitter alerts for the account I need for a graduation project
thanks a lot
Thank you for watching. :D
is it the file in github same with your all series tutorial laravel api ? or theres update which not in youtube ?
The final project with all the code is in the repo.
srry this has nothing to do with the API tutorials but since you work with laravel i wanted to know a basic question, where do you put your logic using laravel? i've been working with laravel for like 6 months at work and i just put all logic in controllers, apparently by reading some forums this is a bad practice, should i use the eloquents model or something else ? thanks.
It really depends on what type of logic it is. There are different tools available for different jobs.
Model specific stuff can go as a helper on the model.
Logic behind validation can be done in custom requests. This can also manage authorisation.
If your controller is simply fetching data to display, then most of that can be done by setting up ORM (Object Relationship Mapping) correctly which means far less db queries in the controller. Which does seem to be a mistake newbees make quite often.
Middleware can also have its uses.
If you're building an API to return data, then use an API resource to transform data like I did here.
Your own custom Facades or Traits are better than the controller most of the time.
If you start using all the other tools available to you in Laravel, you can keep your controller rather simple, and the simple life is the good life.
Thanks Quentin! my fist time with Laravel, and you tutorial help me to organize me a lot.
Just a question, I case that I want to extend the CRUD example to one with record versioning, do you have any recommendations?
Best from Argentina
I'm glad the videos were helpful.
I'm not sure what you mean by "record versioning," perhaps you can clarify?
I did talk about API version in the previous video.
@@QuentinWatt yeah, but I want mean record level versioning
Thanks you bro, can you make a turorial the Passport?
I will very likely do that in future with Vue and Laravel based apps.
This series really should have the word BASIC somewhere in the title. You are teaching a lot of bad habits (raw data for PUT requests and such) and not even covering the basics of some of the many things that will trips people of out of the gate like CORS. Not sure of you plan to follow this series up with more detailed series, but this one in and of itself is almost too basic and as mentioned sends people that do not know any better in a few wrong directions.
The delivery and overall audio/video quality are solid. But those with poor or incomplete content don't help much. Not hating here, just providing feedback for consideration in improvements and future viedos. I know how much time and effort these things can take, so I applaud the effort!
Thank you, your feedback is valuable and I'll take it into account for future. :)
You might want to start with the positive paragraph in future and then lead into the helpful criticism in future though.
I can see you're very opinionated, which is a good thing, but I do feel like it's fairly obvious from the first video that this series is aimed at beginners and you've got to learn to crawl before you can walk. The "bad" all falls under your use case though, as JavaScript apps will use HTTP requests and not FormData.
The point of these tutorials is that they are done in a safe offline environment, away from the stress of production. They cover a lot of ground for someone who has new to Laravel.
CORS will be covered when I have tutorials with apps running on different ports on my local so I can simulate the problem and solution correctly. How I chose to pass data in postman is a simple change and is somewhat of a menial complaint, as that focuses is more from the front end, which was purposely avoided by using postman and not a real form.