Support validations via inheritance

[offirgolan]

Resolves #111

Allows validations to persist through inheritance

const ParentValidations = buildValidations({...});
const Parent = Ember.Object.extend(ParentValidations);

const ChildValidations = buildValidations({...});
const Child = Parent.extend(ChildValidations);

var child = Child.create({...});

child.validateSync(); // should validate all props defined in parent and child

[offirgolan]

ping @rwjblue 😸

[stefanpenner]

don't we usually want to do this on-demand via CP getter?

[offirgolan]

That's what it was before, but because of this line, it goes into an infinite loop.

[stefanpenner]

that is an empty line

[offirgolan]

LOL it changed after I made a commit. See here

For some reason, the getter keeps recomputing and doesnt cache the object, so it keeps calling itself when checking for an inherited validations object.

[offirgolan]

@stefanpenner ready for final review

[stefanpenner]

i think the caches want to be on the instance, not the prototype.

[offirgolan]

Caches were always on the proto. That's how we decided to write them. They are cached by model guid. See test here

[offirgolan]

You can see the code for the cache. If we remove it from the proto, there isnt really a need for this...