Attila Oláh

> when would this be resolved, any particular timeline planned for it. I am kind of reluctant pushing out breaking changes one by one, my hope is to collect them...

Hi @twittwer! No, there is currently no option to do this, all validation rules will be triggered on every property, regardless of the result of the previous ones.

No need to delegate it, it will be implemented in the core.

Hey, this is on my list, I will add it.

The first comment mentions the decorator receives a transformed nested class instead of a plain object. If that is the case, then it's a bug and should be fixed. Note:...

Hi! Can you please provide - the commit where the change was introduced - and your use-case (metadata storage is an internal part of the lib and it's not supposed...

Just chiming in, those functions while deprecated were removed accidentally, 0.5.1 re-added them. However, it's still a good idea to use the new name.

> However when unit testing, these services are registering themselves during tests that don't require them and then beginning their start up routines (initializing connections etc) which causes tests to...

For the original issue, @comprimator was right, this is circular dependency and won't work. I am even surprised you say it runs and you get undefined. Assuming you target a...

> agreed. so i take this as a confirmation that this is not "dead". It's not and won't be, personally, I used all three (typedi, class-validator, class-transformer) libraries for work....