validate() always returns true with constructed custom objects

var schema = new SimpleSchema({ name: { type: String }});
var context = schema.newContext();

context.validate({}); // correctly returns false
context.validate(new Object()); // correctly returns false

function User() {}
context.validate(new User()); // returns true, should return false
context.validate(new (function() {})); // returns true, should return false

[matanlb]

+1 This is a really weird behavior. I don’t understand why this constraint is needed, but even if it is it makes more since to throw an error detailing this then always returning true.

[aldeed]

Thanks for your patience. SimpleSchema 2.0.0-rc.1 is now released and includes changes that resolve this issue.

There are a number of breaking changes when updating to 2.0, so be sure to check out the change log. If you use aldeed:collection2, you will need to use 2.10.0 or higher of that package in order to use SimpleSchema 2.0. If you use autoform, it is not yet updated to work with SimpleSchema 2.0, but hopefully soon.

SimpleSchema is now an isomorphic NPM package, so you can check out the updated readme and file issues over at the other repo. The Meteor wrapper package will exist for now but eventually I will probably deprecate support for it.

This is still a beta/RC and I do expect people will find issues, so use with caution. Production use is not yet recommended. That said, there are more and better unit tests than ever before, and the codebase should be much easier for others to read through and debug quickly.