Donald Mull Jr.

I had the same problem. After reading the code, I found out that the documentation is out-of-date or wrong. It's: ``` Checkit.Validator.prototype.myCustomValidator = function(val) { ... } ```

It's there, it's just documented wrong. My example above shows how to add them.

Please point NPM to your repo where the code for 2.3.0 and 2.3.1 is. It still points to this repo which hasn't had commits since 2018.

Added another property name fix

I, for one, love that idea. Also, put that in some of the first examples people see.

I use ES6 with something like: ``` export class ProductionSheet extends bookshelf.Model { get tableName() { return 'ProductionSheet'; } get defaults() { return { property1: 'blah', property1: null } }...

There are still problems with ES6, especially collections. There are some static functions used that don't get 'inherited'. Models work, though, for the most part.

No, the (ES6) `extends` only does the instance properties (the prototype). None of the statics. Coffeescripts's `extends` **does** copy both the properties on the prototype and the constructor just like...

**UPDATE:** The below code is not actually doing what I think. Some coffeescript classes in the chain screwed it up, not ES6 classes which seem to get .forge(), .collection(), etc....

Yea, I had some coffeescript classes in the mix (don't ask) that cause things to break from 0.8.1 -> 0.8.2 and I misinterpreted the evidence. I finished converting them all...