Middleware
Overview
Middleware is useful for adding other libs for additional features. Local middleware will be replaced with AOP soon.
Note, current middleware API is experimental. There can be breaking changes in next release.
For now, middleware is pretty trivial. You can use @Middleware decorator and define it on route or on whole controller.
Simple example:
1
import { Controller, IController, Get, Middleware, IRouterContext } from "odi";
2
3
const logUrl= (context: IRouterContext, next: () => Promise<any>) => {
4
console.log(context.request.url);
5
next();
6
}
7
8
@Controller()
9
export class SampleController extends IController {
10
11
@Middleware(logUrl)
12
@Get index() {
13
return `Hello, world from index !`;
14
}
15
16
@Get about() {
17
return `Hello, world from about !`;
18
}
19
}
Copied!
Decorators
There are only 1 decorator for middleware purposes.
@Middleware(...functions: MiddlewareFunction[]- set middleware for only one path, or set middleware for whole controller. Accepts unlimited number of middleware functions.
Don't forget about function context. You should set it manually or use lambda functions instead.
Purposes
Unfortunately, due to middleware structure, dependency injection cannot be applied for middleware functions. It should be used only for request data preprocessing, parsing and etc.
Check out future releases for AOP
AOP will solve most middleware cases
Last modified 3yr ago
Copy link