David Ferencz

It seems that there is some problem with the environment and not the `class-transformer` package. The package will try to find the correct type if it has metadata information, which...

To note a few things: - `type declaration is emitted only if some decorator is added to the property.` (so you must add at least one decorator to have type...

Could you checkout a commit from before when it supposadely worked and check if there has been any package-lock.json (or yarn, or pnpm whatever you use) updated? It should work...

@braaar I think this pr should be merged as it just updates the documentation to reflect the current state of the code.

Fixed in https://github.com/typestack/class-transformer/pull/1541

I do not think this should be added. This could cause other issues for existing users of this library. I do believe that this problem should be handled via a...

Hello @kwek20, I assume you would like to extend the current [discriminator](https://github.com/typestack/class-transformer?tab=readme-ov-file#providing-more-than-one-type-option) solution to work on the base abstract class level as well? Is that right? So you would like...

Thank you for the reply, I still have to check if there were any discussion on this topic already, but I think this could be useful. I myself would have...

@kwek20 there is already a really old discussion and pr on this topic. I will try to read through the issue and the pr and maybe we can do something...

Hello @rohitkhatri , If you have 'exposeUnsetFields' set to `true` on the `plainToInstance` method call, you can add an additional `@Expose` decorator on top of your property. In you case:...