Combined FormRequest and Single Action Controller?

[kohenkatz]

I have an application that uses FormRequest classes extensively, in order to ensure that authorization and validation are done. Some of these requests use traits and/or inheritance to include common parameters. (For example, reports can be filtered by specific data points, but all reports can also be filtered by date range and location ID, so they all include FilteredPermittedDateRangeReportRequest which adds the common start and end date validations and authorization/validation for the chosen location IDs.

I also like the idea of Single Action Controllers for cleanliness, because it allows each of the report types to be a self-contained file.

But using these two techniques together means I still have two files - one for the authorization and validation, and the other for the execution.

I'm thinking of creating a common SingleFormController something like this (pseudocode):

abstract class SingleFormController extends Controller
{
    protected abstract function authorize(Request $request): bool;

    protected abstract function rules(Request $request): array;

    protected abstract function handle(Request $request);

    public function __invoke()
    {
        // Check authorization and validation, then execute
    }
}

That can be used like this:

class MyReportController extends SingleFormController
{
    protected function authorize(Request $request): bool
    {
        // Same as the `FormRequest::authorize` method
    }

    protected function rules(Request $request): array
    {
        // Same as the `FormRequest::rules` method
    }

    protected function handle(Request $request)
    {
        // If authorization and validation both pass, execute the code
    }
}

However, this seems to me like it's something the framework should be able to handle already, because 99% of the functionality is already there. It feels like I'd be reinventing the wheel to implement this myself. There's so much that happens behind the scenes when processing a FormRequest, and I'm concerned that my implementation will need a lot of work to maintain the same behavior as I have with just using a form request implementation with a single action controller.

Have I missed a way to do this that already exists? Or should I implement it? Or is it not worth doing?