Fixed #45: custom messages for custom validators

[mattiloh]

I added a test for the 'allow the use of custom messages on failed validation', too.

Unfortunately the test-setup seems not to work well with the promise-based interface of Checkit. Even failing tests are counted as passed and you only see the errors by scanning the test-list for thrown errors. I added a done-callback in a final then(done, done) to the Checkit-Promise of my test to make it work. All other tests should be updated, too. But I'll open an issue for that.

There seemed to be some un-built changes of former commits. So lines 718 + 897 of dist/checkit.js are unrelated to this fix and contain new messages for the field-type integer.

I also added webpack to package.json and changed the npm-scripts build and test to use local versions of mocha and webpack.

[rhys-vdw]

It seems strange that this modifies err. Is there another way?

[mattiloh]

Yes, you're right. I tried another way like this:

var errorMessage = validation.message || err.message;

...

fieldError = errors[key] = new FieldError(errorMessage)

But unfortunately that only works for one validation-rule per field, as it will be only applied if fieldError is still undefined. If there are several errors for one field, the error-objects will just be pushed to the array fieldError.errors (in line 226).

[mattiloh]

I just refined the tests to check for validation-fields with one rule and with several rules. If I try the version without modifying err, it's not passing.

[mattiloh]

Hi Rhys! Are there any suggestions on this?