Native Service class (0.15)

[icebob]

I would like to start a discussion about a new native Service class idea.
As you know the current service class is a schema-based solution, you should write a schema POJO and export it in a JS file.
There is also an "ES6" class solution, the logic same but you should call the this.parseServiceSchema method with a service schema in your service class constructor.

The idea is that you can create your custom class following the guidelines and load it with the broker, or just export it in a service.js file, like the schema-based services. In the class, you can call the methods, action handlers and event handlers directly, as normal class methods.

You should define the main properties as class properties. The action (and event) definitions are also class properties (with a specific prefix).

Here is an example:

export default class MyService extends NativeService {
    // Service name
    name = "my-service";
    // Service version
    version = 1;
    // Service dependencies
    dependencies = ["posts", "users"];
    // Service settings
    settings = {
        foo: "bar"
    };
    // Service metadata
    metadata = {
        a: 5
    };
    // Action Hook
    hooks = {
        before: {
            create: ["validate"]
        },
        after: {
            create: ["afterCreate"]
        }
    };

    // --- ACTIONS ---

    // Action definition
    actionCreateUser = {
        name: "createUser",
        visibility: "published",
        params: {
            username: "string",
            password: "string"
        },
        handler: "createUser", // The name of action handler method, can be omitted if the same as `name`
        asyncCtx: true // The handler method will be called with `ctx.params` as first and only argument. If you need the `ctx` you can get is from AsyncStorage
    };
    // Action handler
    async createUser(params) {
        await this.myMethod(params);
        return params.user;
    }

    // Minimal Action definition, the `name` and handler function name are came from property name without "action" prefix.
    actionListUsers = {};
    async listUsers(ctx) {
        return this.adapter.find();
    }

    // --- EVENTS ---

    // Event definition
    eventUserCreated = {
        name: "user.created",
        group: "user",
        handler: "userCreated" // The name of event handler method, can be omitted if the same as `name`
    };

    // Event handler
    userCreated(ctx) {
        this.myMethod();
    }

    // Methods
    myMethod(params) {
        this.broker.info("Params:", params);
    }

    // Lifecycle handlers with dedicated method names

    created() {
        this.logger.info("Service created!");
    }

    async started() {
        this.logger.info("Service started!");
    }

    async stopped() {
        this.logger.info("Service stopped!");
    }
}

I'm curious to know what you think about it, or any other ideas to improve or change it.

Thanks in advance!