Vlad Poluch
Vlad Poluch
Of course we need doc improvement in this area.
Feel free to contribute :)
You can use groups in this case: ```ts class Field { @IsString({ always: true }) name: string; @IsString({ always: true }) @IsIn(['values', 'numbers', 'dates']) type: 'values' | 'numbers' | 'dates';...
We have some discussion about this validator https://github.com/typestack/class-validator/issues/412. Please try `@IsISO8601()` validator and use date in format `2019-10-04`;
https://github.com/typestack/class-validator/pull/539 fixed multi-dimensional arrays for `@ValidatedNested`. But we should also support multi-dimensional arrays for cases like: ```ts @IsNumber({}, { each: true }) tags: number[][]; ``` Note: I see one edge...
Maybe `@Custom` is not bad idea. But we should avoid add decorators like `@Transform` as this library is about validating not about transform. Use `class-transform` on this purpose.
Currently we do not have support for multidimensional arrays. You have to create your own custom validator.
Sure we use `validatorjs` as main validator library, but we also have own non-string validators e.g. `IsInt` and more. I think we could accept also numeric input for `IsPort`. @NoNameProvided...
@NoNameProvided Why is this breaking change? We can accept both number and string and change is minimal. It is only new functionality not breaking change. Code should be: ```ts export...
😈 yeah `create` without `Promise` will hit DB. Maybe just rename to `createInstance` or just add big note to docs. We have `merge`, `hasId`, `getId`. It will be shame do...