Question: have you considered using `class-validator` for validation?

Is your feature request related to a problem? Please describe.

First, congratulation @4lessandrodev for this great lib 🏅, I really appreciate your work!

In your lib, you declare a Validator class, I think that validation is a topic that is well addressed by some dedicated packages, notably class-validator which provide rich functionalities.

Wouldn't it make sense to rather use such lib rather than writing a custom implementation?

I see those potential benefits:

separation of concern and richer functionalities by using a package fully dedicated to this task
less code on your objects requiring validation for instance on ValueObject (see example below)

Describe the solution you'd like

In your example app, let's take the example of the product-price value object:

import { IResult, Result, ValueObject } from "types-ddd";

export interface PriceProps {
    value: number;
}

export class ProductPrice extends ValueObject<PriceProps>{
    private constructor(props: PriceProps) {
        super(props);
    }

    validation(value: number): boolean {
        return ProductPrice.isValidProps({ value });
    }

    public static isValidProps({ value }: PriceProps): boolean {
        const { number } = this.validator;
        return number(value).isPositive();
    }

    public static create(props: PriceProps): IResult<ProductPrice> {
        const message = 'value must be positive';

        if (!this.isValidProps(props)) return Result.fail(message);

        return Result.Ok(new ProductPrice(props));
    }
}

export default ProductPrice;

With some changes on the ValueObject class (adopting such approach ), this might be simplified to:

import { IsNumber, Min } from "class-validator";

import { ValueObject } from "types-ddd";

export class PriceProps {
  @IsNumber()
  @Min(0)
  value: number;
}

export class ProductPrice extends ValueObject<PriceProps> {}

export default ProductPrice;

4lessandrodev / rich-domain

Question: have you considered using `class-validator` for validation? #22