# Custom endpoint decorator

Custom endpoint decorator could be interesting when you want to handle a request and perform actions before or after the endpoint method.

Unlike Pipes that operate on the parameters of a method, the endpoint decorator will operate on the method itself.

It's based on the middleware and use one of these decorators to work:

  • UseBefore : use the given middleware before the method,
  • Use : use the given middleware after UseBefore but before the method,
  • UseAfter : use the given middleware after the method.

# Built-in

Many other decorators are implemented and can be taken as an example to build your own endpoint decorator. Just follow the links here and click on source link to see source code on Github:

# Build your own decorator

One of the use cases already implemented by Ts.ED is the PlatformAcceptMimesMiddleware :

import {uniq} from "@tsed/core";
import {Constant} from "@tsed/di";
import {NotAcceptable} from "@tsed/exceptions";
import {Middleware, MiddlewareMethods} from "@tsed/platform-middlewares";
import {Context} from "@tsed/platform-params";

/**
 * @middleware
 * @platform
 */
@Middleware()
export class PlatformAcceptMimesMiddleware implements MiddlewareMethods {
  @Constant("acceptMimes", [])
  acceptMimes: string[];

  public use(@Context() ctx: Context): void {
    const {endpoint, request} = ctx;
    const mimes = uniq((endpoint?.get("acceptMimes") || []).concat(this.acceptMimes));

    if (mimes.length && !request.accepts(mimes)) {
      throw new NotAcceptable(mimes.join(", "));
    }
  }
}
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

You can see in this example the usage of endpoint.get from EndpointInfo . This method contains all options which can be passed to the decorator associated to PlatformAcceptMimesMiddleware.

import {Get} from "@tsed/schema";
import {Controller} from "@tsed/di";
import {AcceptMime} from "@tsed/common";

@Controller("/mypath")
export class MyCtrl {
  @Get("/")
  @AcceptMime("application/json")
  public getResource() {
  }
}
1
2
3
4
5
6
7
8
9
10
11

TIP

This example uses AcceptMime decorator with one option, the application/json. This option will be set to endpoint.get seen before with PlatformAcceptMimesMiddleware example and can be retrieved by using endpoint.get(PlatformAcceptMimesMiddleware).

Ts.ED provides API to create your own decorator like AcceptMime which registers the options and at least one middleware with these decorators and utils:

  • Use , UseBeforeEach , UseBefore , or UseAfter for middleware registration,
  • Unable to find something: symbolName === "applyDecorator" if you want to combine different decorators,
  • StoreMerge or Unable to find something: symbolName === "StoreGet" to register options.

For example, we can take the AcceptMime decorator as an example and see how it works. Here is its code:

import {AcceptMimesMiddleware} from "@tsed/common";
import {UseBefore} from "@tsed/platform-middlewares";
import {useDecorators, StoreSet} from "@tsed/core";

export function AcceptMime(...mimes: string[]): Function {
  return useDecorators(
    StoreSet(AcceptMimesMiddleware, mimes),
    UseBefore(AcceptMimesMiddleware)
  );
}
1
2
3
4
5
6
7
8
9
10

TIP

It is also possible to create a custom endpoint decorator without Ts.ED middleware. If your action is really small, you can register a pure express middleware to reach better performance.

import {UseAfter} from "@tsed/platform-middlewares";
import {useDecorators} from "@tsed/core";

export function CustomStatus(code: number) {
  return useDecorators(
    UseAfter((req: any, res: any, next: any) => {
      res.status(code);
      next();
    })
  );
}
1
2
3
4
5
6
7
8
9
10
11

Last Updated: 11/29/2021, 11:14:40 AM

Other topics