Proposal: Introduce PrimitiveValueObject for single-property ValueObjects

Hello,

recently i switched from using ValueOf to this library’s ValueObject class. I have a lot of single-property VOs. ValueOf made it easy for me to create them as everything i had to do was to write a single line like: public class EmailAddress : ValueOf<string, EmailAddress> { }

With ValueObject I have to manually write something like

public class EmailAddress : ValueObject
{
    public string Value { get; }

    private EmailAddress(string value)
    {
        Value = value;
    }

    protected override IEnumerable<object> GetEqualityComponents()
    {
        yield return Value;
    }
}

Every time i create single-property VO i have to write several lines of boilerplate code. I would like to make it simpler by introducing PrimitiveValueObject or SinglePropertyValueObject:

    public class PrimitiveValueObject<T> : ValueObject
    {
        public T Value { get; }

        public PrimitiveValueObject(T value) { Value = value; }

        protected override IEnumerable<object> GetEqualityComponents() { yield return Value; }
    }

With this class i can create EmailAddress like:

    public class EmailAddress : PrimitiveValueObject<string>
    {
        public EmailAddress (string value) : base(value)
        {

        }
    }

Do you think that it would be beneficial to be included in the library? I can create a PR if you like this.

[vkhorikov]

I like the idea too, please go ahead with a PR. Couple notes:

1. PrimitiveValueObject sounds better than SinglePropertyValueObject (more concise)
2. PrimitiveValueObject should be abstract with a protected c-tor.

[MikelThief]

Thanks!