Laravel 11 Route Model Binding: Why the Detailed Error Message Regardless of Environment?

[ozdemirrulass]

In Laravel 11, there's something I find confusing and would like clarification on. When using route model binding, a ModelNotFoundException is translated into a NotFoundHttpException.

In addition to that regardless of whether the debug mode is active or not, or if the environment is set to production or local. The error message directly returns the model namespace and identifier, like:

No query results for model [App\Models\<MODEL_NAME>] <MODEL_IDENTIFIER>

I used a custom ApiException class and implemented custom behavior in app.php to solve it, but this still seems a bit weird.

Can anyone shed light on why this is the case?

[henzeb]

Did you set debug to false as well?

[ozdemirrulass]

"In addition to that regardless of whether the debug mode is active or not"

[noefleury]

About the exception which is transformed to a NotFoundHttpException I think that’s because from a REST perspective the route is not found (but it’s discutable).
For the second question I’m curious too to know the answer, and more particularly when in production.

[ozdemirrulass]

I thought the same. I think it would be better to change the behavior of the exceptions based on the environment.

[Abouelez]

You can override response when ever this exception is thrown,
in bootstrap/app.php you can do that

 ->withExceptions(function (Exceptions $exceptions) {
       $exceptions->renderable(function (NotFoundHttpException $e, $request) {
            if ($request->is('api/*')) {
                return response()->json(['message' => 'Record not found.'], 404);
            }
            throw $e; //for web view
        });
})

[max-shteklia]

@bulletproof-coding Doesn't that mean you have to manually name the resource in every model? I like the way it shows just the model's name; it works perfectly from my project's perspective and doesn't reveal anything. Your point remains valid; I simply don't want to define the resource name manually for every model because, in my situation, it would still duplicate my model's name.

[max-shteklia]

@macropay-solutions Making every route using missing() is a pretty weird approach, in my opinion. Your lib is not overhead for me. I just wanted to change the not found message and found out that in Laravel, there is not a super easy solution for that, and I shared my approach for solving that :)

[macropay-solutions]

@max-shteklia @bulletproof-coding Anyway thank you both for inspiring us.

[ghost]

@max-shteklia

Doesn't that mean you have to manually name the resource in every model?

Yes it does. It helps with auto registering all routes but you have to manually write each resource name in each model you expose.

[macropay-solutions]

You should say {resourceName} not found not model name not found.
GET /actions/{id}
could use Model Payment but the message should say 'Action not found';

That is a valid point too. In my projects, I mostly use route model binding, so my models are according to error messages I need. What defines $e->getModel()::RESOURCE_NAME? I started exploring in the web what this constant is and found nothing; I'm assuming that it is the custom thing you add in your model, am I right? Do you add a RESOURCE_NAME constant to every model?

@max-shteklia now RESOURCE_NAME is optional just like you wanted. https://github.com/macropay-solutions/laravel-crud-wizard-free/releases/tag/3.4.14