invalidkeys() not set when separately constructed schema is included in collection definition of collection2 about meteor-simple-schema HOT 4 CLOSED

Also, a successful update operation returns undefined as well. I don't know it was ever supposed to return something, though.

from meteor-simple-schema.

I added some additional tests, and they seem to indicate this is working properly, albeit not with your exact test schemas, but with similar ones. Is it possible there are errors happening? If a client operation passed validation on the client but then fails validation on the server, the server errors are not propagated back to the client, so invalidKeys might be undefined (although I think it should be []).

Can you post code that provides the simplest possible example that reproduces this every time, including the insert/update calls you are using?

from meteor-simple-schema.

I noticed that thing about the update result being undefined, but it wasn't always happening and I couldn't find any cause. I assumed it was maybe a mongo-livedata issue, but I'll keep an eye on it.

from meteor-simple-schema.

Hmm, this is embarrassing/interesting. I did a meteor reset, cleaned up old builds and rerun the project only to see that it works fine! I should have done my homework better.

from meteor-simple-schema.