-
Notifications
You must be signed in to change notification settings - Fork 11.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception output of missing function in controller is wrong #27344
Comments
Hmm, I can see why this is a problem indeed although I wouldn't necessarily label this as a bug but rather an enhancement. Welcoming PRs which might improve this error message. |
Is it even the good syntax? I mean even if you put a name of existing method it wouldn't work. |
The syntax is correct. I think this is possible since 5.6 or 5.7, not sure.
… Am 30.01.2019 um 17:25 schrieb Inani El Houssain ***@***.***>:
Is it even the good syntax? I mean even if you put a name of existing method it wouldn't work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Yeah it was added here: #24385 |
may be something related to the version of PHP 7.1.20 |
A PR was merged that should address this: #28397 Thanks @570studio |
Description:
When you add a route to a controller function that does not exist, laravel throws a
ReflectionException
instead of aBadMethodCallException
. The exception says that the function()
does not exist.Steps To Reproduce:
web.php
file like this (does not happen when you pass the controller and function as string)TestController
but don't create functionindex
Expected behaviour would be that laravel tells which function does not exist.
The text was updated successfully, but these errors were encountered: