Attila Oláh

+1 against it. Hard to maintain and to moderate. A chat is totally unrelated to Butter.

There is currently no way of doing this. What is your use-case? Why do you accept both `string` and `boolean`? Do you convert it to one of them after validating...

How about a signature like: ```ts @IsType(Array boolean>) ``` ```ts @IsType([ val => typeof val == 'string', val => typeof val == 'boolean', ]) private readonly foo: boolean | string;...

I don't understand, the stack trace will be useless to you because it will originate inside class-validator and not your code. You can already check if your received error is...

Well then you can check via ```ts Array.isArray(error) && error.every(e => e instanceof ValidationError) ``` right?

Nevertheless, as mentioned in other places, the error format will be reworked, but I don't want to start ot monkey-patch it before that.

Hi! I pinned the tab, I will take a look next week.

> Is there a reason why forbidUnknownValues shouldn't be default? It seems like an issue that class-validator has a security vulnerability in it's default state. Historical reason, it is a...

Note to self: handle in class-transformer as well before closing this issue.

> Does "forbidUnknownValue: true" prevent this issue entirely or only mitigate it? @donnd-t It prevents this issue. The `forbidUnknownValue` instructs the class-validator to throw when it encounters any value which...