Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[6.x] Alleviate breaking change introduced by password confirm feature #30389
In Laravel 7.2 the password confirmation was introduced, this feature sadly brought a breaking change with it:
This results in:
The best solution for this would be to disable this function by default but after 15 days this could introduce problems in many live systems. This pull request does the second best solution and enables these routes only if the controller exists.
Because this middleware targets a narrow range of the userbase (just like the VerifiesEmail middleware) I'm also proposing to make these routes disabled by default in 7.x.
I think it would not make much sense since it is directly related to the method itself. Also it is more related to the routes than the auth and currently the route config is the web.php where you can set these options.
Furthermore even if it's decided to be moved that could only happen in the next version.