Implement password reset functionality using Laravel 8 Fortify - Laravel Fortify EP5 

Thank you for your kind feedback

Hey, you are correct on what you're saying. This is the default message from laravel so it could be worth sending them a PR to change that message

@@PenguinDigital It should be known, but I also could make a PR. Thank you

Yeah I agree, probably not the most optimum default message.

@@PenguinDigital I have seen a lot of pages doing this. It should be common knowledge that you shouldnt do this. Sorry for writing this under a video of you, but I just wanted to alert the people that are doing this, that it might be a big problem doing it this way.

No problem Johnny I agree with what you're saying, it's not something I would have implemented myself if I was coding the library from scratch. I can't see the vast majority of people changing the message so it will be down to getting a PR pulled in to the framework to have the maximum impact

Thank you for the feedback

@@PenguinDigital the thing is that you actually have a thankless job on the youtube world. There is a lot of knowledge behind a good tutorial and measured against the views, you often don't achieve that much with it. In fact, the impact of your tutorials is very big because people don't just look through it for a moment - forget everything and don't think about it anymore. this can lead to completely new projects! but even if you(as a viewer) realize that -> mostly you don't bother to comment in the end. I work on myself here and that's why I'll do it at this point ;-) I think your way to present this - which include commandline commands that present how to get the results is very well. The fact that you delete unused content in order to re-implement it just a video later has a clear value because the connections between the individual components become so much more understandable. this is really well done! thanks for that

Possibly in the future yes, I will see what time I have spare

I guess he confused himself but it's password.update that is correct lol

Thank you trik

Hi Rui. Yes sure, you just copy over the assets into the resources/view folder in the exact same way you would in previous versions. There is a built-in artisan command that will do that for you automatically: php artisan vendor:publish --tag=laravel-mail

The part "view:" after "return view(" is just a hint provided by the IDE. It's not part of the actual code.

Sounds like somewhere along the way you are missing an @csrf under a form... maybe.

You can use what ever you like, noreplay is a common one most companies use. Obviously the @test.com will be your own domain

It's not something I've used in production yet but i haven't launched any new products since jetstream came out