notaphplover

Hey @unadlib, Inversify's architecture has their pros and cons. It allows to provide a vast variety of features other libraries simply can't. But as you correctly guessed it comes with...

Closing the issue since no additional details nor a minimum reproduction code were provided. I'm open to reopen the issue once we get more info to diagnose the issue and...

The idea is so cool! Unfortunately, I'm afraid this cannot be done in Typescript, closing issue.

Hey @alecgibson, I'm sorry, I did not read your comment. I'll have a look at your approach, I need some days to carefully think about this enhancement. At first glance,...

Hey @alecgibson , > ```ts > container.bind('Foo').toConstantValue({foo: 'foo'}) // ok > container.bind('Foo').toConstantValue({bar: 'bar'}) // compilation error > > @injectable() > class UsesFoo { > @injectTyped('Foo') > foo: {foo: string}; //...

Hey all, at the end it's going to be a plugin in the [monorepo](https://github.com/inversify/monorepo/pull/59). I'm working on some issues and refactors at this moment, but I haven't forgot about it...

As promised, a [library](https://www.npmjs.com/package/@inversifyjs/strongly-typed) has been published to provide this feature :tada:. I hope you enjoy it. Special thanks to @alecgibson who made this possible.

After having a look at the data, it seems the underlying issue is the lack of a fallback value when providing the attack name. For example, consider https://github.com/tcgdex/cards-database/blob/master/data/Diamond%20%26%20Pearl/Majestic%20Dawn/65.ts: Since their...

Hey @ChristiaanScheermeijer, thank you so much for opening the issue. > We've migrated our codebase to inversify@v7. Thank you for maintaining this library 😄 You're very welcome 😃, I do...

Hey @alecgibson, yeah, but as said, there's not much we can do to check whether or not the behavior is expected or a bug. In this specific case, the cause...