Object::Pad or Class feature?

[ajmetz]

Is there any way to use Object::Pad or the Class feature for our Mojolicious Controllers?
I would love to write method instead of sub, and so forth for the various actions, and not have to have $self in the signatures.
Currently I get a variety of errors when I try to mix the two (Object::Pad and Mojo::Base - or use feature 'class' and Mojo::Base), and am not sure if it's the way I'm trying to establish Mojolicious::Controller as a parent - or if it's an Object::Pad bug, or a Mojo::Base bug, or what...

With Object::Pad....

Inconsistent hierarchy during C3 merge of class 'Management::Controller::Root':
	current merge results [
		Management::Controller::Root,
	]
	merging failed on 'Mojolicious::Controller' at /opt/perlbrew/perls/perl-5.40.2/lib/5.40.2/x86_64-linux/mro.pm line 30.

With 'class' feature...

Class :isa attribute requires a class but "Mojolicious::Controller" is not one

[ajmetz]

Er...spoke too soon!? I appear to now have it working...

use v5.40;
use Object::Pad v0.820;

class   Management::Controller::Root :repr(HASH) {

    inherit Mojolicious::Controller;

    method hello_world {

        $self->render(
            text => "Hello World!",
        );        

    }

}

HTTP::Server::PSGI: Accepting connections at http://0:52000/
[2025-05-21 15:00:06.86950] [2914171] [trace] [Im7w6fmJ0PEY] GET "/hello"
[2025-05-21 15:00:06.87070] [2914171] [trace] [Im7w6fmJ0PEY] Routing to controller "Management::Controller::Root" and action "hello_world"
[2025-05-21 15:00:06.87640] [2914171] [trace] [Im7w6fmJ0PEY] 200 OK (0.00688s, 145.349/s)