Anyone know any nice naming patterns for a paralle...

# random

[Rob Elliot]

Anyone know any nice naming patterns for a parallel class graph, where in one graph the types represent data that is partial or incomplete (or not yet validated?) but the other graph represents complete, validated data?

In the former all or many “required” properties on classes may be nullable, and may have less precise types, and post validation these would be copied into instances of classes representing the complete, validated data.

PartialFoo, UnvalidatedFoo, `IncompleteFoo`… none of those feels quite right, somehow. Is there a standard I’m forgetting / never learnt?

[edrd]

We are using Raw and Processed

[edrd]

Someone posted a link to a validation library where the examples use Draft prefix for nullable/unvalidated types

[edrd]

Could be an option too

[Ruckus]

I tend to use a format like Foo, FooFinal, FooFinalFinal, FooFinalButForRealThisTime, etc.

[Rob Elliot]

Thanks, I like DraftFoo a lot.

[dewildte]

InvalidThing ValidThing

[dewildte]

But I guess it depends on the language in the domain.

[dewildte]

ThingDTO Thing its sounds like you are talking about an anti corruption layer.