Umed Khudoiberdiev

right this feature allow to setup communication easily. Sending all params as separate query params is a big pain. @marshall007 what I do in my apps I usually have lets...

@19majkel94 is right that its just a nice-to-have feature and you can do same almost same way. But I really like this feature because its a bit more elegant and...

nope, lets left it open and wait if someone want to contribute, maybe even @marshall007

routing-controllers allows you to declare routes and functions that will be executed on user's request on that route. Using decorators and class methods. What you are asking is just complexity...

> it's actually one of the requirement of the MVC design pattern, for the controller to be stateless on a request basis actually MVC design pattern is quite abstract does...

okay I've got your idea and request, probably something like this is implementable: ```ts @JsonController({ factory: (request, response) => { const logger = new Logger(request); return new UserController(logger); } })...

right he would need to do something like this: ```ts @JsonController({ factory: (request, response) => { const logger = new Logger(request); const userRepository = Container.get(UserRepository); return new UserController(logger, userRepository); }...

lets say if we do such thing in `typedi` then how do you see it should work, provide more details. How integration should look like and how request/response objects shall...

> I was answering to one controller instance per request problem. yeah, I was talking about same. > I really don't get the idea Imagine you want to log each...

I think what @19majkel94 want to say (and what I say for everyone who come from java/c#) is that in node.js and javascript/typescript we must think more javascript/typescript-ish way. Most...