Incorrect behavior of required attributes.

[Ky6uk]

Current version of this library (0.9.1) uses _.intersection for comparison changed and invalidated attributes. But if no attribute defined in model, we have passing validation for this attribute despite of { required: true } rule.

[platinumazure]

Hi @Ky6uk,

First of all, can you confirm that this is still happening in the current version (v0.11.1)? (I assume it is since I remember seeing that _.intersection code, but it's still worth double-checking!)

Second, can you give us a test case? If you can give us an example of how to trigger this behavior, we can turn that into a unit test and that will help a lot in trying to fix this.

Thanks!