Vlad Poluch

@pleerock Any progress in this feature? Some design, feature spec?

Just adding reference to PR https://github.com/typeorm/typeorm/pull/3768

We are not supporting convert `bit(1)` to boolean. MySQL types `bool` and `boolean` are synonyms for `tinyint(1)`. So by default we are converting only `tinyint(1)` into js `boolean`. You have...

Totally waiting for this feature too!

Looks like this is the way how to libphonenumber library parse strings. From javadocs: > Parses a string and returns it as a phone number in proto buffer format. The...

There are plenty of ports https://github.com/google/libphonenumber library to another programming languages. I hope someone have a similar issue. Maybe check official issue tracker for https://github.com/google/libphonenumber first. Some solution could be...

Hi, I think you could use already exist `ValidateIf` decorator for your case. I updated test case from this PR: ```ts class MySubClass { @MinLength(5) name: string; } class MyClass...

> This ensures I can still do checks on the data even if it's not of the nested type. In a perfect world, `conditions` would be a part of `ValidationOptions`...

I added you because I think this is similar problem as you describe in proposal https://github.com/typestack/class-validator/issues/582. In your proposal you want use already existing `groups` feature and extend it with...

Also adding global validation context we could also remove groups functionality completly. E.g. ```ts class MyClass { @ValidateNested({ condition: (object, value, context) => { return value instanceof MySubClass && context.requestType...