Component Hooks Registering

Mantra follows a microkernel software architecture and acts like a glue for the components in all its essential functionality.

Components can define a number of services, like views, bloks, apis, and the like.

To do so, a component should indicated what exactly registers in onStart method of the component, as indicated in Component Definition section.

This is what we call a Mantra hook.

Each kind of hook is described in the following sections.

As an example, consider this:

class BooksStarter {
    async onStart( MantraAPI ) {
                APIName: "addnewbook",
                APIHandler: BooksApiHandlers.AddNewBook
                CronConfig: "0 */5 * * * *",
                CronHandler: BooksCronHandlers.DownloadAmazonCover
            .Event([ {
                EventName: "users.removed",
                EventHandler: BooksEventHandlers.OnUserRemoved
                Command: "showallbooks",
                Handler: BookViewsHandlers.ShowAllBooks

In this case, a component named as books defines:

  • An API of the name *addnewbook" than will be handled by BooksApiHandlers.AddNewBook method.
  • A cron job for running every 5 minutos that will be handled by BooksCronHandlers.DownloadAmazonCover.
  • It defines an event handler for "user.removed" event; when this event happens, then BooksEventHandlers.OnUserRemoved will be called.
  • A view with the route "/books/showallbooks" that will be handled by BookViewsHandlers.ShowAllBooks method.

Each kind of hook has its own properties, some optionals and other mandatory.

To avoid to type programmatically all hooks for a component in onStart method, some of then can be automatically registered by Mantra by description according to file names definitions, as described in the following sections.