Eivind Fjeldstad

That's interesting. I've never actually used the `+` operators myself. Would allowing something like `.op('+repage', ...)` be enough for your use case?

I don't have a lot of spare time right now, but PR is welcome:)

Yeah, maybe we could allow something like ```js const schema = new Schema({ prop: { type: Object, strip: false } }) ```

No, not currently. For my use case it didn't make much sense because of concurrency issues etc. Do you have a specific use case in mind?

Yeah, I do the same thing, but I like to delegate that stuff to the db layer to avoid race conditions. You can validate fields together (sort of) by doing...

Hmm, that's strange. The published version is compiled with Babel, so import statements shouldn't be an issue. Do you have a stack trace?

No, a flag should not be necessary. I assume you're installing with npm or yarn? It's very difficult to say what might be wrong without a stack trace though.

Hmm, yeah. I'll get it done as soon as i have some time to spare. PR welcome:)

The way required works has changed somewhat in 4.0, mainly for booleans and numbers, but an empty string is still considered invalid. It seems to me that most people are...

Yeah, I agree it's not ideal. It's also a road block for a sane default value implementation (#33). I like the idea of separating `required` from `empty`.