Comments (3)
Hi @WClouds
Could you share a Minimal reproduction of the problem, so I can solve it.
but I just tested the simple loggerMiddleware
with the example provided with Nest Router Repo, and it just works fine.
from nest-router.
@shekohex I still can't get it to work.
The example in the repo sets up the middleware for the other modules in the main App Module, but in my case I have a few modules, and each sets up its own middleware.
For example, in the main App Module I set up the routes:
// app-module.ts
const routes: Routes = [
{
path: '/my',
module: MyModule,
},
];
@Module({
imports: [
RouterModule.forRoutes(routes)
])
export class AppModule { }
However when I do the following in MyModule, the middlewares are not actually being set up (called) for the module's routes:
// my-module.ts
consumer.apply(MyMiddleware).forRoutes(MyController);
// my-controller.ts
@Controller('path')
export class MyController {
@Get()
async action(): Promise<any> {
return;
}
Calling GET my/path doesn't trigger MyMiddleware.
I tried moving the routes definition to MyModule, but that doesn't work either.
When setting up the middleware like above, should the consumer take into account the prefix set in the AppModule?
Or any other idea why this doesn't work?
from nest-router.
@Metheny80 please see the README.
but you should instead use this code
consumer.apply(someMiddleware).forRoutes(RouterModule.resolvePath(SomeController));
from nest-router.
Related Issues (20)
- There is no such a word like childrens in english HOT 1
- Params in nested routes and swagger HOT 3
- Difference to nestjs RouterModule ? HOT 1
- How to use versioning in v7? HOT 1
- dynamic path intercepts static HOT 4
- Require controller and http method instead of module HOT 1
- Intercepter per route (module) HOT 3
- An in-range update of @nestjs/core is breaking the build 🚨 HOT 3
- An in-range update of @nestjs/core is breaking the build 🚨 HOT 1
- Route resolving fails when setGlobalPrefix() is used HOT 5
- Nest-Router Adding Additional Slash before Controller HOT 4
- An in-range update of @nestjs/core is breaking the build 🚨 HOT 1
- Route gets double slash when try to define root level routes; `//users` instead of `/users` HOT 6
- Add a name to the routes HOT 3
- Defining routes as both nested and top level HOT 3
- Lack of documentation HOT 1
- Nested modules does not retain prefixes. HOT 2
- Child routes with parent modules HOT 2
- Question : What are the drawbacks of having route prefix at controller level instead of module level ? HOT 2
- [Problem] Order of evaluation of routes is the other way round HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nest-router.