Laravel Routes: Grouping and Other "Tricks" - Challenge Result
HTML-код
- Опубликовано: 5 сен 2021
- Let's discuss some Pull Requests after last week's challenge, I will mention the main things I've noticed there.
Original video with the challenge: • New Laravel Challenge:...
See all 50+ Pull Requests: github.com/LaravelDaily/Larav...
- - - - -
Support the channel by checking out our products:
- Enroll in my Laravel courses: laraveldaily.teachable.com
- Try our Laravel QuickAdminPanel: bit.ly/quickadminpanel
- Purchase my Livewire Kit: livewirekit.com
- View Laravel Code Examples: laravelexamples.com
- Subscribe to my weekly newsletter: bit.ly/laravel-newsletter 
Хобби
Great video, learnt loads more than I thought I would! Love the “use” grouping!
Sorry to hear about your daughter, hope she is getting better.
Yes she is getting better, at home now for 5 weeks, thanks for the support.
I use name() instead of as() and that works too. I personally think it's more expressive and straightforward.
Your channel is awesome and very interesting, keep it up.
I'm learning a lot of new tips with those challenges!
Thanks for your effort and hope your kid is doing better.
Yes she is getting better, at home now for 5 weeks, thanks for the support.
Royal like from me, and send email notification before these challanges
Thanks, again new informations. Thanks. I hope Your family is OK.
really insightful video
Great Exercise!
I think that if you're doing route resourse, you should stick to everything as it is, without changing names of routes and other stuff, otherwise it becomes unreadable mess.
As to using slugs, I think it's better to decide whether to use slugs instead of ids everywhere for that particular model. In that case there's a Route::bind() method or resolveRouteBinding() method if you want to use it on the model
Once it is a big project and there are hundreds of routes, in my opinion it will be efficient to separate routes on files and register them inside RouteServiceProvider.
For ADMIN it will be a file
One thing I noticed is not many people put their method chains on new lines. As such you end up with really long lines for each route, and I noticed you having to scroll sideways a lot in this video still. To me that seems like a problem because it's harder to read, to take the whole route in, and your git diffs will be harder to understand too over time as the routes grow and change. I'd say partly it's just my personal preference to use a lot of newlines, but there's definitely benefits to keeping lines short in this file in particular.
Thanks as always!
@jeytii My man thank you so much for that shortcut, i tried to search that shortcut but couldn't find any docs or blog. All this is because of Sir Povalis for these challenges. RESPECT
Your videos are helping a lot. It would be good if you make a video on Laravel Cashier in 2021. 🙏
Not sure what my video would do that is not written in the official Cashier documentation :)
Thanks for the challange and the good afford in the videos. They’re all great and inspiring. I hope your daughter gets well soon!
If you have time, I wonder your opinions about PR#16. I tried to create a new approach.
Interesting approach. But, in my personal opinion, it's unnecessary over-engineering with losing of readability for typical Laravel developers, they would be confused why routes are made very differently from a typical Laravel approach.
Loved the 'use' grouping on namespaces. Gotta utilize that thing soon and will pretend to be a pro laravel dev 😎😁 (kidding)
Super guru
Great movie like always. It is possible to prepare material about returning exception, errors with Controller + Service? I mean the good practice of returning errors with a VueJS and Laravel.
ruclips.net/video/SlBJrLnyoMk/видео.html maybe this video would help, also search the channel for "exceptions", you will find more videos
Nice.
Great Videos, Thanks for the precious resources.
Request: Do a code review of Workice CRM or any other advanced Project which do not use laravel traditional filesystem. I have tried navigating through the project but its all new to me whereas I have been a laravel developer for 2 years now. I already have license purchased if you need that.
I don't like and don't prefer Laravel projects that don't use Laravel traditional file system, so not going to review them.
@jeytii great shortcut for grouping
You should start using PHP Storm it suggests that by default.
Can you make a simple livewire/alpine wizard form tutorial? Im new to livewire and i dont know the best use cases. Thank you for making your videos, you are awesome!
From what I remember, I have something on my livewirekit com
Is there any code snippet for adding images using polymorphic manytomany with product? E g. For each (files as image){ $product->images->attach($image)}
Good evening, how can I implement a JSON Rest API for getting and searching data (with pagination) ?
I left a comment on #54 about something on your challenge that I tried to do but couldn’t. Was there something we could have done regarding those update routes using post methods?
Another thing that I was kinda unsure and was a topic mentioned here was about setting the namespace of the routes folder to the controller folder and don’t deal with use statements at all.
My decision for committing to that was that the project only had a single folder for controllers and since routes usually leads to controllers it felt like a goodbye approach at the time. I’m not sure if that violates PSR or it could cause trouble and confusion in the future.
No, those methods are not supposed to be in resource, cause their behavior is different from default Resource Controllers. With setting the namespace - not sure, I haven't seen anyone doing it, I guess it's the case of "if it doesn't break anything, it's probably ok" :)
@@LaravelDaily awesome! Well, I cannot remember another time that I was stuck for that long on a single Laravel documentation page. It was a very clever challenge despite its simplicity.
Well done and I hope everything gets well soon regarding to your daughter.
I was expecting my PR (#33) to be seen :(
I saw many PR missed to separate books.show from 'auth' middleware.
Although I did enjoyed the challenge.
Also prefer 'name' over 'as' for naming routes.
Sorry, I was unable to discuss majority of PRs, I spent 5 days last week in a hospital with my daughter, with very small online time at all.
Now I've looked at your #33, and you did a lot of things right, but didn't do the very first thing I expected - extract long controller path names on top into "use" statements.
Yeah, I did saw your tweets about the incident :(
I pray everything gets well soon
Hey!
Route::middleware(['auth', 'verified'])->group(function () {
Route::resource('photo', 'PhotosController')->withoutMiddleware('verified');
});
Where do you stand on this?
I'm ok with this, but personally never had a case where I needed to use it.
Sir, Please tell us which theme of phpstorm you are using. The code very prominent and easy to readable. I want to use this theme. Please tell us.. Thanks
Material darker
@@LaravelDaily Thanks
Currently, 2021-10-06, the video it's not in the 'Laravel challenges' - Playlists.
Thanks, fixed.
@@LaravelDaily No problem, you are undoubtedly the MVP here. Thanks!
What is {book : slug} in route parameter and how to use it? Thanks.
It's route model binding: laravel.com/docs/10.x/routing#customizing-the-key
Thanks
What about mine? 😊