Umed Khudoiberdiev
Umed Khudoiberdiev
> Also I think that importing all from directories by glob string is an antipattern loading entities / controllers / anything else from directories is efficient, productive and pragmatic solution...
As I understood your only arguments are: * how to disable specific middleware * how to handle order of middleware execution Your first argument isn't an issue. You just need...
> I always do index files as it's great in combination with tsconfig.json "Path mapping" feature and tsconfig-paths module - you can have nice readable imports then: import { AuthMiddleware,...
> You complain about index.ts looks bad in folder structure but you don't use outDir and have , *.js, *.js.map and *.d.ts files for each *.ts source file in each...
As I already told go ahead guys if you really need this way of importing 😄
guys sorry for a small of-topic, but before discussing this I have a question. What did we decide with calling "next" after each controller action? As I remember last decision...
I don't know other use cases. Probably this question needs some research in exist express middlewares
okay so what is resolution on this issue? Do you decided to go with original proposal in first message, or is something changed with interceptor proposals? Or do we change...
We need to decide if we remove after middlewares or not before implementing this PR. Because if we do remove after middleware we don't need proposals in this PR
If we remove after middleware we don't need this functionality since separating before and error middlewares does not make any sense