notaphplover

Hey @alexleboucher, we are putting all our effords in building better http libraries. These effords are reflected in the monorepo. We will write an entry in the inversify blog announcing...

Hey @acommodari, it's hard to do a roadmap when contributing in my spare time. Tbh, I don't feel in the mood of coding these days. This is not related to...

> @notaphplover I just wanted to post to ask if there were any updates? And equally, if there's anything I or others can usefully do to contribute at the moment?...

Hey @suhailsalim, thanks for your kind words. I'm doing great these days 🙂. > If you need extra hands on something, would love to help out! Actually I do! I'm...

Hey guys, I finally released the http packages. You can finally use them as they are described in the [docs](https://inversify.io/http/). Your feedback would be super valuable, if you see any...

Hey @egmacke, > is there an equivalent in the new version of AuthProvider, and httpContext? (We made extensive use of it when extending from BaseHttpController - mostly for identifying the...

Hey @egmacke, > The biggest thing that inversify-express-utils HttpContext gave was the ability to access this information in every controller method without having to inject the raw Request object into...

I'm afraid this is not an inversify issue. `@inject` is a legacy decorator and, as such, it doesn't exist as a js decorator. Typescript transpiled code don't emit a decorator...