FortJs is a MVC framework which means the application will be divided into three parts - Controller, view, model.

A route is mapped with Controller and will target a Controller method.

So route in fortjs has two parts -

• Controller - A class
• Worker - A method inside a class

How to decide what part of route will target controller and worker ?

Consider an url - "abc.com/user/add" and let's split it -

• abc.com - domain of the website
• /user - controller route
• /add - worker route

Let's take another example - "abc.com/user/1/2/3" and split it again -

• abc.com - domain of the website
• /user - controller route
• /1/2/3 - worker route

but you can also make some part of worker route as controller depends upon the requirement

e.g - The above route can be also breaked as -

• abc.com - domain of the website
• /user/1 - controller route
• /2/3 - worker route

Let's see how the route is configured in fortjs -

Controller Route

In order to create a controller route we must have a controller. This controller is mapped with a path.

e.g - Consider you have created a controller, let's say - "UserController".

You need to map Controller with a path.

import { Fort } from "fortjs";
import { UserController } from "./controllers";

// here we have mapped UserController with path "/user"
Fort.routes = [{
    controller: UserController,
    path: "/user"
}]

Fort.create();

In the above example we are mapping "UserContoller" with a path "/user" inside the "routers" member of App. Since UserController is mapped with "/user", so controller route is - "user".

Note :- If you have large no of controller (let's say more than 10), it is recommended to define routers in a file as array (you can also divide your routers into multiple files)and then import those inside class App. The motive of this note is to keep your routers clean.

Worker Route

Worker route is mapped to a Worker inside Controller. e.g -

Creating Worker Route

Let's say we want to create the worker route "add" - you need to create a method with the name "add" and add decoarator "Worker" above it . The decorator "Worker" add the method to route list with method name -

import { Controller, Worker, textResult } from "fortjs";

export class UserController extends Controller {
    @Worker()
    async add () {
       return textResult("add is called");
    }
}

So, When url will be - "abc.com/user/add" then add method will be called.

Customizing route

By default route is name of method, but you can customize the route using decorator "Route". The "Route" decorator is used to customize the route in multiple ways -

import { Controller, Worker, textResult, Route } from "fortjs";

export class UserController extends Controller {

    @Worker()
    @Route("/addCustom") // changing the route name
    async add () {
       return textResult("add is called");
    }
}

You can see in the code , we have used 'Route' decorator to override the route. So, now when url will be - "abc.com/user/addCustom" then add method will be called.

Restricting the worker based on http method

Currently with any of http methods (GET,POST, etc.) "add" method will be hit. But let's say you want to hit this only when http method is POST.

In this case - you need to provide desired http methods to worker. Let's see an example -

import { Controller, Worker,textResult,HTTP_METHOD } from "fortjs";

export class UserController extends Controller {

    @Worker(HTTP_METHOD.POST) // This method will be only hit when any of the http method specified in worker will match.
    async add () {
       return textResult("add is called");
    }
}

Single route & multiple http method

How about you want to create a route "add" which will hit different worker based on http methods. This pattern is highly used in rest api implementation . Let's see an example -

import { Controller, Worker, textResult,HTTP_METHOD, Route } from "fortjs";

export class UserController extends Controller {

    @Worker(HTTP_METHOD.GET)
    @Route("/add")
    async addWithGet() { // This will be called when method will be GET
       return textResult("add with method get is called");
    }

    @Worker(HTTP_METHOD.POST)
    @Route("/add")
    async addWithPost() { // This will be called when method will be POST
       return textResult("add with method post is called");
    }
}

Params in route

1. Constant param :

So far we have created a route - "abc.com/user/add". How about little more complex route - "abc.com/user/add/1".

For this, we just need to modify our route.

import { Controller, Worker, textResult,HTTP_METHOD, Route } from "fortjs";

export class UserController extends Controller {

    @Worker()
    @Route("/add/1")
    async add () {
       return textResult("add is called");
    }
}

2. Variable param :

In the url - you can see "1" is the constant value but for certain requirements - the place where 1 is present can be any value.

e.g - "abc.com/user/add/2", "abc.com/user/add/hi", "abc.com/user/add/1000" etc.

Basically a part of the url is a variable which can hold any value.

You can declare a variable in a route by using {}. Let's see -

import { Controller, Worker, textResult,HTTP_METHOD, Route } from "fortjs";

export class UserController extends Controller {

    @Worker()
    @Route("/add/{value}")
    async add () {
       const value = this.param.value; // placeholder values are present in 'param' member of the controller.
       return textResult("add is called");
    }
}

3. Variable & Constant :

How about a route where you want to return some file based on some extension.

e.g - "abc.com/file/scripts/jquery.js" . In this example - "jquery" is variable value and ".js" is constant value

So here :

• controller route is - 'file'
• worker route is - 'scripts/jquery.js'

import { Controller, Worker, textResult,HTTP_METHOD, Route } from "fortjs";

export class FileController extends Controller {

    @Worker()
    @Route("/scripts/{fileName}.js")
    async getScripts () {
       const value = this.param.value; // placeholder values are present in 'param' member of the controller.
       return textResult("add is called");
    }
}