Instead of removing Database from the form request, you could have used "nullable" validation property. BY this, you could also use $request->validated() method while creating user.
Not a fan of how you moved the success check into the view like that. I mean I am all for a shorter controller too but I don't like the idea of having actual logic the the view even though it was a simple in_array check on another variable that was passed in. I personally try to stick to using only variables passed in from the controller and anything blade provides for itself like if's and loops. Maybe an occasional helper function call, but only if necessary.
@@LaravelDaily In a way I'm glad to hear that because I'll catch myself looking at code I wrote months ago and wondering what I was thinking. Good to know I'm not alone in that.
I really like how it looks, but since you still have to start from the commandline (generate key), I would probably have made the installation there. Besides grouping the routes I think I would move them to a separate file as well. But it does look nice!
Actually it seems a bit complex for me. I definitely prefer to use one or two controller for setup. Also private methods are ok but for readability i prefer helpers. So i definitely agree with you.
Amazing video series. Congratulations !! I coded almost 20 years back :) and now I am working on a real estate portal. I learned laravel 8 a bit and have reached a respectable stage of the project. Now I am facing some issues on the frontend . What technology you suggest for front end which has small learning curve and with good documentation ? People talk about vue js , react js etc and you also have some videos on livewire. Which is the better option for me ? Your advice will be a great help for me.
Just yesterday, I tweeted: twitter.com/PovilasKorop/status/1405117715522666506 It's YOUR decision. Invest a day reading about how EACH of them work (just read the general documentation and program simple "Hello world") and you will understand what you like more and what is more fit for your project.
I haven't worked on such project where each user would have their own smtp settings. I would even say it's pretty dangerous to allow them to have their own settings.
@@LaravelDaily In my project, there are many admins. All of them seem to be confidants. And they have a list of owned users. And they need to send letters on behalf of the administrator, tell me, what exactly is it dangerous, or where can I read it?
I can't answer this in a short RU-vid comment. I mean, in general, allow users to change core config of your system is dangerous, in theory. But actually, this exact repository, in this video, has an example of overriding the config with custom values, so I guess you should follow the same strategy.
Thanks a lot sir for your contribution ..I really appreciate knowledge shared by you.( best laravel teacher ).🙏 please sir start one series laravel 8 with interia stack. Beginning to expert ..
Hi , Laravel WhereIn query, how many value can we use to filter the records . Is it possible to use 4k value inside the whereIN (id, [....]). Please advice.
@@LaravelDaily Yes, true. But for more code formatting like with Observers & Services. When you register a user a code goes right from observer and if he wants to send a new code, excecutes service.
