Incorporating oneOf Validation in class-validator

[AbdlrahmanSaberAbdo]

I noticed a previous discussion (issue) where someone inquired about the possibility of implementing a oneOf validation feature in the class-validator library. I've encountered a similar scenario in which I needed to utilize oneOf validation, so I implement a custom validator for it. However, I believe it would be beneficial to have a built-in decorator specifically designed for oneOf validation within the class-validator library.

I would appreciate your input on whether this feature aligns with the goals and scope of the class-validator library. I believe incorporating this feature would be useful.

Here's an example of how we can use oneOf

class TypeA {

    @IsString()
    public foo;
}

class TypeB {

    @IsString()
    public bar;
}

class Parent {

    @IsObject()
    @ValidateNested()
    @OneOf([() => TypeB, () => TypeA])
    public child: TypeA | TypeB;
}

Here's the old issue on oneOf GitHub Issue #616

Looking forward to hear inputs & opinions on this