🔗 #[RouteParameter] does not bind your model

If #[RouteParameter] in your Laravel form request receives a string instead of a model, it's often not about failed binding but about the absence of binding altogether. Laravel's #[RouteParameter] attribute enhances type safety but only reads the current route parameter value. It does not perform route model binding, which means if the controller doesn't provide enough information for implicit binding, the form request might get the raw route string instead of an Event model.

This article dives into the nuances of using #[RouteParameter] in form requests and highlights why it's crucial to keep the model in both the controller method signature and the form request constructor. It articulates a vital point: Laravel relies on the controller's method signature to perform implicit route model binding. Without it, the model won't be resolved correctly, potentially leading to errors. Understanding this can save developers from common pitfalls in Laravel's routing and request handling.